OCZ Vertex 120 and sleep cycling problems with MacOSX 10.5.6 (9G55)

[mikest]

Hi,

I ordered an OCZ Vertex 120 last week and installed it in my MacBook Pro (non-unibody, MacBookPro4,1) and has been going swimmingly except for one problem. After the machine has gone to sleep, the drive will no longer respond after waking up. It's fairly reproducible (somewhere around 1 in 3 attempts of sleep cycling), and once the drive goes it requires a hard reset to get the machine to respond again.

I also notice that if I enable "Put hard disks to sleep when possible" that sometimes the drive will fail to respond after the OS tries to wake it back up again.

If I disable drive sleeping, and I don't put the machine to sleep I have no problems with the SSD and it stays responsive.

The OS version is Mac OS X 10.5.6 (9G55).
Drive information is:
OCZ VERTEX 00.PT1:
Capacity: 121.6 GB
Model: OCZ VERTEX 00.PT1
Revision: 00.PT1

After forcing a hard reset, Disk Utility reports that /private/var/run/pcscd.pub
is corrupt, and has the wrong block size.

Thanks!

[MikhailT]

That might explain why I don't have any issues with Vertex. I always turn off put drive to sleep in Macs as a habit even with regular HDD. But as I understand, you still have the problem even with that feature turned off. But I have no issues whatsoever with sleeping. The only difference between us is that i have 1199 firmware in my 120 vertex.

It might be an issue with hibernation. Try to use this app, http://www.jinx.de/SmartSleep.html and turn off hibernation. See if that fix your issue.

[mikest]

SmartSleep is an interesting workaround tool, thanks!

Actually, I have been able to successfully get the machine to recover after disabling sleep and *only* using hibernate (not surprising, as this performs a full power down.)

Unfortunately hibernate on OSX is slow, and undesirable for on the go laptop usage. I'm mostly looking to help OCZ find a way to have the SSD come back up after being told to sleep like a regular HDD.

[stylinexpat]

I turned off putting my hard drive to sleep. Have not had any problems with it.

[harshw]

Hi,

I ordered an OCZ Vertex 120 last week and installed it in my MacBook Pro (non-unibody, MacBookPro4,1) and has been going swimmingly except for one problem. After the machine has gone to sleep, the drive will no longer respond after waking up. It's fairly reproducible (somewhere around 1 in 3 attempts of sleep cycling), and once the drive goes it requires a hard reset to get the machine to respond again.

I also notice that if I enable "Put hard disks to sleep when possible" that sometimes the drive will fail to respond after the OS tries to wake it back up again.

If I disable drive sleeping, and I don't put the machine to sleep I have no problems with the SSD and it stays responsive.

The OS version is Mac OS X 10.5.6 (9G55).
Drive information is:
OCZ VERTEX 00.PT1:
Capacity: 121.6 GB
Model: OCZ VERTEX 00.PT1
Revision: 00.PT1

After forcing a hard reset, Disk Utility reports that /private/var/run/pcscd.pub
is corrupt, and has the wrong block size.

Thanks!


sudo pmset -a hibernatemode 0

and then


sudo rm /var/vm/sleepimage

Should help.

[AppleUser]

The problem is that Hibernate is part of the end user experience.

Rather than help OCZ produce a product that requires lots of faffing - I want OCZ to produce a product that follows Apple user's experience.

I therefore expect certain things that have to follow the Apple norms. In the long run it will make OCZ kit better in terms of integrating with OSX - opening a possibility of OCZ approaching Apple.. especially if their current SSD vendor has issues..

[Tony]

Appleuser

We are working thru a few minor issues...it seems to be more platform specific as i can sleep the SSD here in my laptop under Vista no issue and I tested this on desktop yesterday.

This makes it hard to nail down what is actually happening...

for now if the guys have a work around for you i would try it and watch the forum over the next weeks to see if we find anything in FW

[AppleUser]

Appleuser

We are working thru a few minor issues...it seems to be more platform specific as i can sleep the SSD here in my laptop under Vista no issue and I tested this on desktop yesterday.

This makes it hard to nail down what is actually happening...

for now if the guys have a work around for you i would try it and watch the forum over the next weeks to see if we find anything in FW

Yup - I've disabled the HD sleep, I'll leave the hibernate and see if I get any issues appearing.

I've not had an issue with waking from sleep so far since installing, the problem I have had is out of the blue when on AC power but idle. If a problem occurs then perhaps that will help narrow down with real world evidence.

Just to clarify - I have a degree and over 12 years of commercial software development/management experience from firmware to large deployments. So if you have any diagnostic software you want to run alongside, I don't mind helping test.

[sschuldt]

FWIW

I've got the same setup on a Unibody MBP and have had no issues with sleep.

[mikest]

Tony,

Sleep cycling characteristics of Vista and OSX are different. The problem is also intermittent (probably timing related) so it may not reproduce every time. You'll want to try and repro on a late model non-unibody MacBookPro. I will try and collect some better diagnostics about what state the OS is in when it locks up.

Also, make sure you're not using an external enclosure to try and repro. External drive controllers may mask the problem.

Thanks!

[Tony]

FWIW

I've got the same setup on a Unibody MBP and have had no issues with sleep.

this is the problem, one has an issue and another does not....same drive same FW?

[AppleUser]

I think the first thing would be to map who has issues in terms of Model number. So if you're a new 5,1 then you may not have an issue whereas a 3,1 may. The difference I believe is that the 5,1 uses nVidia whereas the Intel chipset.

What would be a nice controlled test is if we know anyone that uses bootcamp with vista and gets lockups with OSX but not when running Visa. Same hardware, different OS.

[AppleUser]

Just a quick google of "ICH8-M AHCI lock ups" returns quite a few hits on lock ups, for example:

https://bugzilla.redhat.com/show_bug.cgi?id=464559

Perhaps the ICH8-M chipset has issues? My poor MBP has the duff nVidia 8600M GT chipset which has solder issues (hence no gaming!).

This one points it's finger at high load causing it..

http://kerneltrap.org/index.php?q=mailarchive/linux-kernel/2008/7/25/2676414/thread

[harshw]

I would like to think that the problem is somehow the fact that the 1199 firmware supports SMART and maybe has something to do with power management. Anyone else had problems even after turning off power mgmt for the drives ? ( i.e. untick "put hard disk to sleep" )

I have turned off hibernate - I did this for saving wear and tear on the SSD anyways - and unticked the box. Have not had a repeat of the freeze up so far. Fingers crossed.

[AppleUser]

The second freeze occurred whilst editing a word document with the "put hard disk to sleep" unticked.

[mikest]

The second freeze occurred whilst editing a word document with the "put hard disk to sleep" unticked.

Was it unticked when the OS started up, and had you gone through a sleep cycle? I've only seen this particular issue once the drive has gone through a sleep cycle. If it spins after a cold boot without sleeping first then that would be interesting.

It's also important to distinguish between this hang, and other OSX hangs ;) One symptom of drive non-responsiveness is that an app will appear to be hung trying disk IO, and other apps will be appear fine until they too attempt disk IO. I call it a "tar-baby" effect, since touching the disk cause the app to get stuck.

I'm installing a second drive in my laptop (thank you MCE!), I might be able to get a trace running and catch this in the act. Knowing what its stuck on would be useful.

[AppleUser]

As stated - Word hung then XP hung, then OSX. This is the same install of word/xp that has been running flawlessly - it's my work and gets used over 37hours/week/48 weeks a year etc for at least 3-4 years. Parallels has been stable for a long time, the only difference has been (a) TM restore of that from backup on SSD reinstall, (b) the installation of the SSD itself (1199 came on the SSD from the factory).

Yup if the OS or the application is performing retries then it's usually a sign that the operation has timed out or the previous operation got a form of temporary failure.

[loud]

till now i got only one freeze after sleeping and i often close the lid but now i am worried if and when the next endless spinning wheel will occur.

i did a hard reset and found no information in the logs that the system switched to sleep mode. perhaps the ssd freezed immediately after closing the lid.

my sytem:
vertex 120 with fw 0112
macbook 5,1 (unibody 2.4ghz 4gb ram)
os x 10.5.6

[MikhailT]

I think you guys won't see anything in the logs as the writes are going into the cache first and if the SSD got frozen before it completes the flush, it would never make it to the logs.

[FieryFurnace]

I didn't have any problems yet with sleeping and my white MacBook (ICH8-M with Vertex60GB 1190) uses the default sleep settings and I close the lid often, but never leave it closed longer the one hour and the battery never ran out.

Should I change the sleep mode (only sleep or only hibernate) or leave it like it is to prevent freezing?

[PWCI]

On a MacBook Pro 4.1, I installed a 250 GB OCZSSD@-1VTX, it worked fine but never could get the system running from sleep mode (either from closing the lid or from the command).
The initial installation was made from the clone of my previous SATA HD.
I suspected a potential problem with the transfer of data and config from a cloned "different" drive.
For testing purpose I reformatted the drive and installed The original Mac OSX 10 software that came with the MacBook Pro, and made all the updates.
With a clean install it works like a charm and very fast, no problem with freezing and/ or delay.

Based on this above, it my be wise to advise to only use "clean Install"

[stylinexpat]

On a MacBook Pro 4.1, I installed a 250 GB OCZSSD@-1VTX, it worked fine but never could get the system running from sleep mode (either from closing the lid or from the command).
The initial installation was made from the clone of my previous SATA HD.
I suspected a potential problem with the transfer of data and config from a cloned "different" drive.
For testing purpose I reformatted the drive and installed The original Mac OSX 10 software that came with the MacBook Pro, and made all the updates.
With a clean install it works like a charm and very fast, no problem with freezing and/ or delay.

Based on this above, it my be wise to advise to only use "clean Install"


I also did a clean install and have no problems. I usually like to shut the computer off and since it only takes 2-3 seconds to shut off I'm happy :)

[MikhailT]

I also did a clean install. I did see somebody post a thread about having issues when he tried to restore from superduper.

[mikest]

The drive suddenly stopped responding on the bus while in use. Now it doesn't show up with diskutil or on the bus probe. Wtf??? Sending back to Newegg. Not impressed :(

[Tony]

Do not send it to newegg, let OCZ handle the rma so we can take a look at the drive.

If you send it to the egg it will get lost in inventory and we will struggle to find it and see if the drive just had a hardware issue.

can you please create a support ticket under ocz.com support tab and then PM me the rma details?

[bugout]

Tony, while I understand your point, my 250GB replacement from newegg is already "out for delivery" from UPS before anyone at OCZ has even responded to the ticket I created yesterday morning..

[AppleUser]

Just upgraded to Parallels 4.0. Spent the morning working/upgrading then started working with MS Office etc as per normal.

Just now whilst editing a word document the machine hung - first XP then OSX completely hung. Still with 1199..

[AppleUser]

And again... a freeze..

[Tony]

Tony, while I understand your point, my 250GB replacement from newegg is already "out for delivery" from UPS before anyone at OCZ has even responded to the ticket I created yesterday morning..

Thats bad, I will have words, they should have responded same day.

PM me your ticket number

[Tony]

And again... a freeze..
you not flashed to 1275 yet?

i have 2 mac guys telling me 1275 sorted their issues

[AppleUser]

you not flashed to 1275 yet?

i have 2 mac guys telling me 1275 sorted their issues

I was going to wait until there's general consensus - since I didn't notice any issues since disabling the hard disc power saving.

I did note there's also an Intel driver update for windows - perhaps there's some power state workarounds in that (there's a C-state fix in there) that may be applicable to OSX too.

The problem for MBP users (and something to bare in mind for firmware updates for Mac users is that the hard drives are often squirrelled away. In the case of the older MBPs (such as 3,1 Santa Rosa) you have to demolish the machine to get to it!

[AppleUser]

And.... yet another hang.

I think I may have to leave work early, go home, backup and patch the drive on my games PC followed by a complete restore installation. I'm not getting any work done - every time I start I loose my work..

[Tony]

Just flash the drive...how will I know you need an RMA if you won't follow the support suggestion?

Please flash it, fresh install to it and test again.

Do not image the drive for the test..fresh install here, all fresh drivers etc.

[AppleUser]

Well I have no option to flash the drive now. I got home, connected TM - backed up the drive then shut the MBP down. On restart to plug my RAID0 drives for offloading the 32GB VM file... the vertex has corrupted the HFS+ volume with "Invalid record count". So I've lost my work VM completely.

I have one of the hangs showing the end of the I/O in Activity Monitor on my phone.

*slight minor rant* This is the drive as it came supplied - without any flashing. This is the only time I will refer to this - regardless of performance I expect it to work first and foremost. Especially as this is the factory shipped firmware without me flashing it!! *end of rant*

I hope I still have my VM copy on the external drive from the time I installed the SSD.. luckily I've been sending my work documents to people.. so the lost 1.5 week of work shouldn't be so much of a problem.

I'll flash tonight and restore *fingers crossed* ;) - see where we go from there.

The demonstration of general performance in my laptop has raised some eyebrows at work - especially the regional guys from europe, US that are looking at SSDs that are reliable and quick to help the technical demonstrations to our customers. Based off the general feel of the general SSD devices I'm not ready to propose them to replace server hardware yet as they're can't deliver the uptime.

[Tony]

These SSD's are not enterprise class, we advertise them as consumer grade...so do i recomend you put them in a server...NO

Why are you guys even looking at Vertex for server application?

Flash the drive and clean install... NO restore yet..i want fresh data on that drive with a freshly aligned partition/drivers and apps.

Please

[AppleUser]

These SSD's are not enterprise class, we advertise them as consumer grade...so do i recomend you put them in a server...NO

Why are you guys even looking at Vertex for server application?

Flash the drive and clean install... NO restore yet..i want fresh data on that drive with a freshly aligned partition/drivers and apps.

Please

Not specifically Vertex for server.

At the moment windows seems to recognise the 'yabadaba-rom' but the flash program can't enumerate it.

OK, after doing the update driver to non nVidia drivers trick - the drive is flashed and recognised with the correct firmware version. XP could create an MBR on it.

Now over to the Time Machine Restore installation..

[AppleUser]

Hmmm now - I can see the drive. It's been repartitioned to GUID by the Disc Utility but the Time Machine restore does not provide it as a replacement destination!!

Will investigate further...

Got it - if the drive does not appear in the TM restore destination, then follow the normal install steps on the SSD but at the point it shows the X disk and asks if you want to continue.. go back. I think this sets the drive up.

[AppleUser]

I've also taken some photos so I can make a guide :)

[harshw]

The demonstration of general performance in my laptop has raised some eyebrows at work - especially the regional guys from europe, US that are looking at SSDs that are reliable and quick to help the technical demonstrations to our customers. Based off the general feel of the general SSD devices I'm not ready to propose them to replace server hardware yet as they're can't deliver the uptime.

I don't think one could use OCZ drives in servers in their current form, but I do hope - and would love - if OCZ made server variants. So 120GB drives would be sold as say 100GB but the 20GB would be available for wear levelling. And customised firmware. Let's hope it happens !

[D111]

Serious server drives have 50% of cells set aside for wear leveling.

They are priced 4X to 10X the price of desktop drives.

[harshw]

Serious server drives have 50% of cells set aside for wear leveling.

:yikes: oh wow, that is being serious about wear levelling.

Anandtech's tests have shown that SATA is not as efficient a protocol as SAS is so I am wondering that perhaps SSDs need to come with SAS interfaces as well.

Can someone from OCZ confirm that if the drive is formatted with 50% of the capacity then the remaining capacity is automatically used for wear levelling ?

[Tony]

you need a FW that sets that much...we could produce a FW that sets 30GB for use and 90GB for wear leveling on a 120GB just for you :)

LOL

20yrs life ;)

[harshw]

you need a FW that sets that much...we could produce a FW that sets 30GB for use and 90GB for wear leveling on a 120GB just for you :)

LOL

20yrs life ;)

ROFL.

But seriously, I think this could be very good for the enterprise segment. SSD's with firmware that sets 33% or 50% to wear levelling. Also they would be faster during heavy usage due to less need for compaction during writes. The average lifespan of a HDD in server usage is 1-3 years anyways. If SSDs can last that long and 4x SSDs can replace 12x HDDs - I think there will be a lot of happy people in server rooms.

[AppleUser]

I think people would look to increase the duty rate - especially for the cost. We do have a couple of products which use large enterprise SANs using RAM/flash as hard drive based SANs can't maintain the required performance. For the remainder of the products we'll use HD based SANs or local drives.

[AppleUser]

Just as reference - complete hang again with 1275 last night. This time it was busy doing a windows update.

[harshw]

Just as reference - complete hang again with 1275 last night. This time it was busy doing a windows update.

So it was in VMWare or it was in Windows ? And anything in console log ? Was it the spinning beachball and machine was unresponsive ?

[AppleUser]

So it was in VMWare or it was in Windows ? And anything in console log ? Was it the spinning beachball and machine was unresponsive ?

The entire machine. Windows Update, Windows, OSX and the beach ball. The only thing that would work is moving the mouse pointer and the power button.

[harshw]

The entire machine. Windows Update, Windows, OSX and the beach ball. The only thing that would work is moving the mouse pointer and the power button.

Yup, that is how it hangs. Which leads me to believe it is somehow the OS - SSD interaction rather than any hardware. Because it hangs the same way across all the models of the MB/MBP.

Yet the hangs are quite random and I have not seen any pattern to them. I dont get more than 1 lockup per week. What about you ? Are they more frequent than that ?

[AppleUser]

Yup, that is how it hangs. Which leads me to believe it is somehow the OS - SSD interaction rather than any hardware. Because it hangs the same way across all the models of the MB/MBP.

Yet the hangs are quite random and I have not seen any pattern to them. I dont get more than 1 lockup per week. What about you ? Are they more frequent than that ?

Two initially but nothing till yesterday..

Yesterday 6 in one day - corrupted the OSX drive completely (the MBP wouldn't boot). It was extremely lucky the reboot was after doing a TM backup of my personal stuff! Only the work VM was unrecoverable (although I have a weekly backup).
I flashed to 1275 and at the end of the evening the machine hung again.

Often I'm just doing something trivial such as editing a word document.. Yes they're occurring in XP/parallels which may be providing a higher i/o rate to the OSX file.
I have 4 GB of RAM and only 1.5GB is configured for the XP VM. So it's usually fine without paging swap or thrashing the drive as the OSX memory free is soaking up i/o by caching.

[AppleUser]

As requested by Tony - I've sent the logs, the photos and the system profile etc information to him.

[mikest]

you not flashed to 1275 yet?

i have 2 mac guys telling me 1275 sorted their issues

Tony,

Where do I find 1275, and is it possible to flash from the mac? I have no windows machines atm.

So, does the Vertex have a thermal protection circuit? The machine was very hot when it froze and dropped off the bus. The next morning I was able to mount the drive, albight with massive HFS volume bitmap corruption :/

Fortunately, I back up frequently ;)

[mikest]

These SSD's are not enterprise class, we advertise them as consumer grade...so do i recomend you put them in a server...NO

Why are you guys even looking at Vertex for server application?

Flash the drive and clean install... NO restore yet..i want fresh data on that drive with a freshly aligned partition/drivers and apps.

Please

Not to sound negative here, but that's a pretty weak distinction and not an attitude that makes me terribly comfortable using this product. Long term storage should be reliable, even for consumers. OCZs marketing literature makes many allusions claiming it as such. If OCZ is releasing incomplete firmware on drives into the market, that's pretty irresponsible.

I'm using mine for video editing, which can thrash a disk harder than most server apps and is very much a "consumer feature".

[Tony]

We have to designate the difference between consumer and enterprise/workstation use...all manufacturers do this.

Now if the end user wants to use a consumer grade product and use for enterprise use then he has to be aware there are risks in doing so. Testing and building to enterprise levels goes quite a bit further then consumer grade products...look at server mothers vs desktop boards as an example.

[D111]

A passenger car is a consumer grade product.

Some are used for taxis, livery services, delivery vehicles. Clearly commercial applications.

Some are used intensely --- like the ultimate soccer parent mobile that is shuttling people from 6am to midnite.

This application is not commercial.

But it will wear out a vehicle no different from commercial use.

Things are no different in the SSD world.

[AppleUser]

Folks - this is degenerating into an argument. Put simply (and everyone will agree):
1. The customer is always right.
2. The customer wants a product to work (fit for purpose).

The CEO of OCZ has already stated that he wants stability first. So as long as he delivers it then I don't have a problem (disregarding the argument about if the product firmware should be available to the market).

[RyderOCZ]

Where do I find 1275, and is it possible to flash from the mac? I have no windows machines atm.http://www.ocztechnologyforum.com/forum/showthread.php?t=52848

You will have to boot from some type of Windows type "shell" in order to flash or connect it to a PC. We do not have a flasher that will run in MacOS yet.

[harshw]

Folks - this is degenerating into an argument. Put simply (and everyone will agree):
1. The customer is always right.
2. The customer wants a product to work (fit for purpose).

The CEO of OCZ has already stated that he wants stability first. So as long as he delivers it then I don't have a problem (disregarding the argument about if the product firmware should be available to the market).

ROFL AppleUser, the first company that I would think of not agreeing on any of those two points would be ... APPLE ! :lol:

To paraphrase you ...
1. The customer is always right ( unless Apple is more right than the customer )
2. The customer wants a product to work ( fit for Apple's deemed purpose )

:deviltail

[FieryFurnace]

http://www.ocztechnologyforum.com/forum/showthread.php?t=52848

You will have to boot from some type of Windows type "shell" in order to flash or connect it to a PC.
We do not have a flasher that will run in MacOS yet.

Does that mean that there might be one some day? You are working on one? :thumbs:

[MikhailT]

For those of you who haven't seen it,


Post here your results, concerns, problems etc.

Notice to mods...all other threads to be merged here please.

Edit 26th March 09


Some info regarding 1199 and 1275...mini changelog.

1. APPLE MAC – Hibernation : Indilinx was able to reproduce it 1 out 10 trials.
A. So, they are fixing the FW bug. Hope(its proving hard to find) this will be revised at the next FW.

Mac users, I suggest if you do have this issue to not use hibernation at this time and NOT allow the SSD to be powered down in power management.

http://www.ocztechnologyforum.com/forum/attachment.php?attachmentid=9242&stc=1&d=1238185091

[MikhailT]

Had a hard crash last night for the first time in the life of Vertex 120gb, it froze with no chance of recovering. Rebooted it, 24 hours so far no issues. This is 2 weeks without any issues. As soon as i finally install a new virtual machine with XP in parallels, blam it all froze up after a while in that vm.

Will try it again once i get my new 2tb external drive so that i can back up the system and run Parallels again to see if it'll cause that hard freeze.

[AppleUser]

Had a hard crash last night for the first time in the life of Vertex 120gb, it froze with no chance of recovering. Rebooted it, 24 hours so far no issues. This is 2 weeks without any issues. As soon as i finally install a new virtual machine with XP in parallels, blam it all froze up after a while in that vm.

Will try it again once i get my new 2tb external drive so that i can back up the system and run Parallels again to see if it'll cause that hard freeze.

I had two hard lockups without any real commonality to create on demand since the 1199->1257 flash. I have powersaving switched off but I've not disabled hibernation.

I'm not sure but I get the feeling it's either:
a) Something in the firmware locking up after a period of time.
b) Heat soak build up causing the MBP chipset to overheat.

Although it's occurred when my smcFanControl is showing 40degC.

[harshw]

Had a hard crash last night for the first time in the life of Vertex 120gb, it froze with no chance of recovering. Rebooted it, 24 hours so far no issues. This is 2 weeks without any issues. As soon as i finally install a new virtual machine with XP in parallels, blam it all froze up after a while in that vm.

Will try it again once i get my new 2tb external drive so that i can back up the system and run Parallels again to see if it'll cause that hard freeze.

Anything in logs ? This problem is so ... random. And it doesnt leave anything in the logs. That is what makes it so annoying.

[D111]

I'm not sure but I get the feeling it's either:
a) Something in the firmware locking up after a period of time.
b) Heat soak build up causing the MBP chipset to overheat.

Although it's occurred when my smcFanControl is showing 40degC.


You got a good hunch here....

We have had reports of failures that sound like SB overload - i.e. taking out every drive attached to the SATA at the same time.

If it reads 40C out of a .10 cent sensor, what must be the real temperature / surge at?

The way to get at this issue is to see if it only occurs under intense load -- heavy writing, reading.

[MikhailT]

Anything in logs ? This problem is so ... random. And it doesnt leave anything in the logs. That is what makes it so annoying.

None. It won't leave any logs because if the SSD or the SB chip is overloaded, there will be NO logs appearing at all because it's blocked from writing/reading which means its a hardware issue not a software issue.

[Eggcake]

First off, I just want to make clear that I don't want to get an advantage of the OCZ Support without having an OCZ product - I just want to help resolve things. Since I didn't read anywhere else about this specific lockup, I just add it here, hoping to help to resolve the problem:

I am using a S*****T***** UD in my Notebook (HP Compaq 6910p, ICH8-M) and having the same issues. Sometimes it works, often it doesn't:
after putting the Laptop into Standby (not hibernation) it won't wake up again. Screen stays black --> powerbutton to force shut down. Of course I can't find anything in event logs.

As I mentioned above: I don't expect any help, I just want to help you guys to resolve the problem.

[AppleUser]

You got a good hunch here....

We have had reports of failures that sound like SB overload - i.e. taking out every drive attached to the SATA at the same time.

If it reads 40C out of a .10 cent sensor, what must be the real temperature / surge at?

The way to get at this issue is to see if it only occurs under intense load -- heavy writing, reading.

Well the chipset is the ICH8-M and limited to 1.5Gbit so it it wouldn't surprise me if the limitation is a thermal one.. Apple stopped calling them laptops because people started getting very uncomfortable with them on their laps!

[D111]

Remember the infamous nVidia chipset recall?

One of the ways we use to get an older MBP compatible is to send it in for the recall --- which got a late model mobo installed... end compatibility problems.

[AppleUser]

First off, I just want to make clear that I don't want to get an advantage of the OCZ Support without having an OCZ product - I just want to help resolve things. Since I didn't read anywhere else about this specific lockup, I just add it here, hoping to help to resolve the problem:

I am using a S*****T***** UD in my Notebook (HP Compaq 6910p, ICH8-M) and having the same issues. Sometimes it works, often it doesn't:
after putting the Laptop into Standby (not hibernation) it won't wake up again. Screen stays black --> powerbutton to force shut down. Of course I can't find anything in event logs.

As I mentioned above: I don't expect any help, I just want to help you guys to resolve the problem.

Have you checked the Intel drivers for Windows for the ICH8-M chipset - there's a few bug fixes for the C-state changes. C-states are used to switch between the bus power saving modes. The nVidia NF2 chipset had the same issue when the northbridge first started using C-states to switch the CPU on or off for powersaving and 'cool running' .. back in the days of the Barton..

[AppleUser]

Remember the infamous nVidia chipset recall?

One of the ways we use to get an older MBP compatible is to send it in for the recall --- which got a late model mobo installed... end compatibility problems.

No guesses which chipset my MBP is running... hence my fixation for keeping it cool.. but it was out of warantee before they admitted there was a problem.. and with me replacing the HD now .. too much time passed to get it replaced.

Although I may see check to see if they'll do the swap (they mention it has to have failed before they'll do it).


GeForce 8600M GT:

Chipset Model: GeForce 8600M GT
Type: Display
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0407
Revision ID: 0x00a1
ROM Revision: 3175

[D111]

it was out of warantee before they admitted there was a problem.. and with me replacing the HD now .. too much time passed to get it replaced.


Apple have been known to twist and bend on warranty coverage when customers appear at an Apple store dressed as a US Marine, with bloodshot eyes, knife clenched between teeth, M-16 at the ready.....

In UK, would have to dress like an SAS man that just spent 6 months behind enemy lines.

[AppleUser]

Apple have been known to twist and bend on warranty coverage when customers appear at an Apple store dressed as a US Marine, with bloodshot eyes, knife clenched between teeth, M-16 at the ready.....

In UK, would have to dress like an SAS man that just spent 6 months behind enemy lines.

I can do the 6 months look on the monday morning at 6am..

[Eggcake]

Have you checked the Intel drivers for Windows for the ICH8-M chipset - there's a few bug fixes for the C-state changes. C-states are used to switch between the bus power saving modes. The nVidia NF2 chipset had the same issue when the northbridge first started using C-states to switch the CPU on or off for powersaving and 'cool running' .. back in the days of the Barton..


Yup, checked - newest chipsetdriver installed. Maybe I check again later if I missed a driver, but I don't think I really did... :)
The only other thing that's different: I'm running on IDE-Mode not AHCI.


@8600M GT

Hehe that's kinda funny. I never heard of that Problem before - the last weekend, a friend of mine, who bought a Dell XPS 1330 about 1.5 years ago, having a very similar GPU destroyed his laptop too. Green/Red stripes --> 2 hours later --> black. He rarely used it :/ I read somewhere else that some 8xxxM-Models got thermal issues which could be fixed using a BIOS Update.

[jerry]

None. It won't leave any logs because if the SSD or the SB chip is overloaded, there will be NO logs appearing at all because it's blocked from writing/reading which means its a hardware issue not a software issue.

No logs is the most annoying part.

I got a unibody MacBook Pro 15 on Friday, and didn't use it until late Saturday night. I installed a 250GB Vertex on Sunday. I had my first of many sleep related crashed on Monday. No lost data... yet.

What I've been able to figure out so far is that I noticed that if it's been put in to sleep for more than an hour it will nearly always hang upon wake. Everything runs, but anything that needs disk I/O is blocked. Processes run until they need disk, then they hang. Nothing can be done except for a power down, and nothing gets logged.

So I've been running top in one terminal and top -au in another terminal, so I can see disk / network activity as soon as I wake the laptop. Not much was uncovered there. But menu meters has given me a clue. What I've noticed (no logs of course) is that it doesn't seem to hang on a read, it seems to hang on write. Once you do more tasks, it will also get a pending read request. But I've noticed that the first "hang" seems to be on write.

In this disk I/O bound state, I stopped top, and tried to run it with different options, and got a "unable to allocate memory." That got me looking at something else......

Now... I've got 4GB of RAM in this, and have never used more than 2GB so far, with 2GBish free at all times. But I still have a 64MB swap file.

Does anyone know if MacOS touches the swap file upon wake, just to make sure that it's there and "happy"?

My current theory is that the drive may not be able to do a write upon wake until either a certain amount of time, or unless a read happens first. One would assume that such operation would be rare. I mean, what other operating system powers up the drive and does a write a half second later, without doing a read first? I only test this as I use my Lappy in daily use. The >1 than hour wait to reproduce and possible problems and wasted time in having to recover/restore makes me not want to push my own testing any more than just my daily normal use.

[jerry]

I should also kick the question out there:

Does anyone know if this drive has a capacitor to back up the cache ram that needs a certain time to charge upon power up before the drive can do a write?

[D111]

Does anyone know if this drive has a capacitor to back up the cache ram that needs a certain time to charge upon power up before the drive can do a write?

Tony will have to confirm this. But I believe there is a capacitor.

However, I do not know if the capacitor is used in the manner noted above.

Guessing here, I would say that the capacitor do not have sufficient capacity to "flush" the DRAM buffer on power out, but merely allows for an orderly powerdown with no "crash" or unrecoverable crap data.

Work it out - with 64megs of data, it can take a while to flush. There is not a capacitor that appear to be that big in there.

[jerry]

Tony will have to confirm this. But I believe there is a capacitor.

However, I do not know if the capacitor is used in the manner noted above.

Guessing here, I would say that the capacitor do not have sufficient capacity to "flush" the DRAM buffer on power out, but merely allows for an orderly powerdown with no "crash" or unrecoverable crap data.

Work it out - with 64megs of data, it can take a while to flush. There is not a capacitor that appear to be that big in there.

Yeah, that's all we can do is guess. I'll fan the flames of speclulation and say that if I were building that drive I would design for worst case. So based on the following benchmarks that I unscientifically generated it could take up to 6 seconds to flush 64MB of random 4k blocks out to the flash. That's assuming the drive actually
doesn't use the write back cache when XBench asks it to.

Sequentail
Uncached Write 107.34 MB/sec [4K blocks]
Uncached Write 73.06 MB/sec [256K blocks]
Uncached Read 27.47 MB/sec [4K blocks]
Uncached Read 213.24 MB/sec [256K blocks]
Random
Uncached Write 11.08 MB/sec [4K blocks]
Uncached Write 87.77 MB/sec [256K blocks]
Uncached Read 5.37 MB/sec [4K blocks]
Uncached Read 151.07 MB/sec [256K blocks]



But if *I* were designing an SSD drive, and had the potential to get 64MB of dirty write buffers in cache RAM that I had to "stick somewhere" in the event of power loss using only capacitor power, I would have "dump area" on the main flash drive interleaved out across all or most of the main flash chips (for raw write speed) that I would keep erased and ready where I could dump (possibly ignoring wear leveling just in that area, for speed) that cache RAM using stored capacitor power in the event of power loss. That dump would be sequentail write, and could complete in less than 1 second. Then, upon power up, the firmware would search that "dump area" and load it back in to cache ram (so it could be flushed out properly in due time) while the capacitor charged, and then re-init the "dump area" before doing anything else. I'm not sure how I would handle the delay while I waited for the capacitor to charge.

But I'm not a hard drive firmware designer.

If *I* were designing the SSD hardware to do the above, I would choose a capacitor large enough to flush the cache ram before it's voltage dropped below the value needed to do the job of flushing/writing. That would be large enough to require an inrush limiter to charge it up. Otherwise, the capacitor would look like a dead short to the drive power supply. A constant current component would be best, but a simple resister would do if one could do with it taking longer to "top off" the capacitor. Either way, physics dictates that the power to the SATA device is finite, and there needs to be enough power left over to actually operate the SSD while the capacitor is charging.

But I'm not an SSD hardware designer.

So there is a time constraint on the charging of the capacitor. What do you do if you've got a pile of data dropped in to the buffer during that time? There isn't sufficaint power in that capacitor yet to gaurentee that data in cache ram can be flushed to disk? You've got to enter some mode to cope with that, and limit performance somehow until things are in a "sane and stable" state. It might only be for a few seconds, but it's nessasary if you're in the business of preserving data.

These are why people that design storage devices get paid the big bucks.

[D111]

But if *I* were designing an SSD drive, and had the potential to get 64MB of dirty write buffers in cache RAM that I had to "stick somewhere" in the event of power loss using only capacitor power, I would have "dump area" on the main flash drive interleaved out across all or most of the main flash chips (for raw write speed) that I would keep erased and ready where I could dump (possibly ignoring wear leveling just in that area, for speed) that cache RAM using stored capacitor power in the event of power loss. Then, upon power up, the firmware would search that "dump area" and load it back in to cache ram (so it could be flushed out properly in due time) while the capacitor charged, and then re-init the "dump area" before doing anything else. I'm not sure how I would handle the delay while I waited for the capacitor to charge.

But I'm not a hard drive firmware designer.

If *I* were designing the SSD hardware to do the above, I would choose a capacitor large enough to flush the cache ram before it's voltage dropped below the value needed to do the job of flushing/writing. That would be large enough to require an inrush limiter to charge it up. Otherwise, the capacitor would look like a dead short to the drive power supply. A constant current component would be best, but a simple resister would do if one could do with it taking longer to "top off" the capacitor. Either way, physics dictates that the power to the SATA device is finite, and there needs to be enough power left over to actually operate the SSD while the capacitor is charging.

So there is a time constraint on the charging of the capacitor. What do you do if you've got a pile of data dropped in to the buffer during that time? There isn't sufficaint power in that capacitor yet to gaurentee that data in cache ram can be flushed to disk? You've got to enter some mode to cope with that, and limit performance somehow until things are in a "sane and stable" state. It might only be for a few seconds, but it's nessasary if you're in the business of preserving data.

These are why people that design storage devices get paid the big bucks.


I do not know for sure --- but I think the Indillinx is nowhere near this complicated.

The more you try to "recover" the cache, the more risk you take of data corruption during the marginal power conditions.

Sheerly on design principles, I would not do it that way, but I don't work for Indillinx.

The safety margins required would far exceed the capacitor given the available form factor even before issues of glitches going from regular power to capacitor is considered.


Oh... about the big bucks... [ NO COMMENT ]

[jerry]

I do not know for sure --- but I think the Indillinx is nowhere near this complicated.

The more you try to "recover" the cache, the more risk you take of data corruption during the marginal power conditions.

Sheerly on design principles, I would not do it that way, but I don't work for Indillinx.

The safety margins required would far exceed the capacitor given the available form factor even before issues of glitches going from regular power to capacitor is considered.


Oh... about the big bucks... [ NO COMMENT ]


Yeah, but if you did the cache flush as a sequentail write, you could do it in a second or less. Sorry, I forgot to mention that, so I edited my post to reflect that.

As I said, I'm not a hardware or firmware designer, nor do I pretend to be one on TV. So my way of doing it is probably not nearly as cleaver as how it actually works. But regardless, there *IS* a period of time when that capacitor is charging where the drive can't function at speeds/latencies like it normally would. It's just a matter of physics. "Not enough power, captain!"

[D111]

Yeah, but if you did the cache flush as a sequentail write, you could do it in a second or less.

But regardless, there *IS* a period of time when that capacitor is charging where the drive can't function at speeds/latencies like it normally would. It's just a matter of physics. "Not enough power, captain!"


One second is eternity when the capacitor may only be 5mm in diameter.

Most capacitors I know do not age graciously, so the safety margins designed in have to be quite large.

Writing is also when the SSD is drawing max power.

As for the latter problem, that is handled by giving the "drive not ready" signal until it is charged.

[jerry]

Here's some real troubleshooting. I expect I'll get some real answers out of this.

Left this running when I slept my Macbook, knowing full well that it'd lock up when I opened it. I had to type this out on another machine, since the disk I/O was locked, while both fans screamed and both cores sat at 100%.

tail -f /var/log/systemlog

17:39:11 kernel[0]: AFPSleepWakeHandler: going to sleep
hibernate image path: /var/vm/sleepimage
sizeof(IOHuvernateImageHeader) ==512
....
lots of stuff that I didn't want to type out
....
17:39:14: kernel[0]: System SafeSleep
17:39:14: kernel[0]:hibernate_page_list_setall start
17:39:14: kernel[0]:hibernate_page_list_setall time: 154ms
17:39:14: kernel[0]:writing 364492 pages
17:39:14: kernel[0]:image1Size 500499456
............
lots more stuff that I didn't want to type out
.................
17:39:14 hibernate_write_image_done(0)
17:39:14 sleep
21:03:47: kernel[0]: Wake reason = EC KID0
21:03:47: kernel[0]: System Wake
21:03:47: kernel[0]: vmmon:powerStateDidChange flags = 0x82 (state 4)
21:03:47: kernel[0]: Previous Sleep Cause: 5
21:03:48: kernel[0]: MVEthernet::mediaChanged - Link Down
21:03:48: kernel[0]: FSLogMsgOrder Last]
21:03:48: kernel[0]: IOBlockStorageDriver[IOBlockStorageDriver ]; executeRequest: request failed to start!
21:03:48: kernel[0]: disk0s3: resource shortage
21:03:48: kernel[0]: kernel[0]:

In another window, top -au was running, and the Disk I/O section showed about 10,000 reads/sec. No Kbytes. Writes not incrementing. Both CPUs to 100%.

[MikhailT]

21:03:48: kernel[0]: disk0s3: resource shortage

what the hell? it thinks it ran out of space?

disk0s3 is vertex drive right?

Now everybody who is getting the freezes once a day should do this as well. leave terminal running with the tail -f command visible on screen at all time so that we can get an idea of what's going on.

this is best done with a second monitor so that people can do all the work on screen 1 with all the information is shown on screen 2 so that it is easy to show everything.

[jgo]

Now everybody who is getting the freezes once a day should do this as well. leave terminal running with the tail -f command visible on screen at all time so that we can get an idea of what's going on


How widespread is this problem? Does it affect every mac user? All versions of FW?

I ordered a 250GB Vertex which should arrive in a few days. If it is a known bug, then I hope Mac users will be better supported with this issue than they are with firmware flashing.

[MikhailT]

How widespread is this problem? Does it affect every mac user? All versions of FW?

I ordered a 250GB Vertex which should arrive in a few days. If it is a known bug, then I hope Mac users will be better supported with this issue than they are with firmware flashing.

We don't know, that's the problem. Mac users are smaller market and combine that with even smaller OCZ ssd market. Not to mention not every mac user will come to OCZ forums. So as far as I can see, it looks like less than 10 mac users come to this and actually say something.

The hibernation issue is a known firmware bug, unfortunately it is very hard to find the bug according to Tony, it is found in 1 out of total 10 experiments that Indirix did. They are currently hunting it down but any information we find here, will benefit them as well.

[jerry]

21:03:48: kernel[0]: disk0s3: resource shortage

what the hell? it thinks it ran out of space?

disk0s3 is vertex drive right?

Now everybody who is getting the freezes once a day should do this as well. leave terminal running with the tail -f command visible on screen at all time so that we can get an idea of what's going on.

this is best done with a second monitor so that people can do all the work on screen 1 with all the information is shown on screen 2 so that it is easy to show everything.

Or just pull those windows to the front just before you sleep the machine, so if it doesn't come back, it will at least show you why. If it does come back, put terminal in the background, and be glad you didn't crash.

disk0s3 is the volume "Macintosh Hard Drive" on the only partition on the 250GB Vertex. I don't know what the kernel thinks, but according to top -au it was doing 10,000 + read operations each second. And the byte counters weren't incrementing. So something is seriously broken there.

I've set my MacBook to hibernate only. I'll see if it survives the night.

[jerry]

I should also add some details:

I've disabled my sudden motion sensor, I've unticked "Put hard drive to sleep when possible" under both power adapter and battery settings.

That was the config I was in when I generated that log that I posted.

Since then, I've realized that secure virtual memory was on, so I turned that off, and I've now set it to hibernate.

I'll see how it gets through a few more sleep/hibernate cycles.

After talking to someone that routinely solves storage problems on an enterprise level, his thoughts were that the drive is probably doing something not quite following spec (perhaps sending something similar to NOT READY TRY AGAIN) to the OS/SATA controller, and the SATA controller/OS is not quite exactly following spec on what to do when it hears that particular NOT READY TRY AGAIN request.

Another valuable tidbit of advice was:

"Ask them if there is a way to put the IOBlockStorageDriver ktext into a more verbose debug mode"

[MikhailT]

i use "sudo fs_usage -f fs" to see what is really going on in the file system.

It's late right now, I haven't had the time to really look at this, for debugging info.


http://developer.apple.com/technotes/tn2004/tn2124.html

[FieryFurnace]

How widespread is this problem? Does it affect every mac user? All versions of FW?

I ordered a 250GB Vertex which should arrive in a few days. If it is a known bug, then I hope Mac users will be better supported with this issue than they are with firmware flashing.

I have a white MacBook (intel ICH8-M Sata I) with an Vertex 60GB, and I'm using my MB for 6-10 hours a day without any problems for more than two weeks.

[harshw]

Since then, I've realized that secure virtual memory was on, so I turned that off, and I've now set it to hibernate.



That causes the swapfiles to be encrypted .. leading to a lot of file ops. I think it also encrypts the sleep image.

[harshw]

Another valuable tidbit of advice was:

"Ask them if there is a way to put the IOBlockStorageDriver ktext into a more verbose debug mode"

Or maybe if the Indilinx engineers can give us an API, we could write a kext for debugging the drive ... The last 65536 commands executed by the drive would be a start perhaps ...

[jerry]

That causes the swapfiles to be encrypted .. leading to a lot of file ops. I think it also encrypts the sleep image.

Why would that lead to a lot of file ops? How would that have any bearing at all on the number of file ops? Crypto or not, if you don't need to page out, you won't. If you do, you will. Either way, the pages are still compressed before they're paged out to the pagefile.

I don't run windows. OS X boxes don't just randomly swap for no apparent reason. Except for creating a single 64MB pagefile at boot, They only page out when they're actually out of RAM.


I'm not crashing after I wake it from hibernation. Except that waking from hibernation takes longer than booting from being shut all the way down.

[duky]

I had a similar issue with my OCZ Apex 120G (I would post the link to the thread I started but it seems to have been deleted) but the most support I got for it was to use SmartSleep and that helped but still was not an adequate solution for me. I also started noticing other problems with the drive so I decided to upgrade to Vertex 120G. I haven't had any problems with it so far even though I no longer have SmartSleep.

One thing I noticed is that the time I had Apex I installed OS X and restored from backup, yet this time I did not restore the entire machine from backup and have not seen any problems. Perhaps there could be issue with some of the system files from previous drive?? I have no idea, just speculating..

This is all on a Unibody MB 2.4 GHz by the way.

[jerry]

I had a similar issue with my OCZ Apex 120G (I would post the link to the thread I started but it seems to have been deleted) but the most support I got for it was to use SmartSleep and that helped but still was not an adequate solution for me. I also started noticing other problems with the drive so I decided to upgrade to Vertex 120G. I haven't had any problems with it so far even though I no longer have SmartSleep.

One thing I noticed is that the time I had Apex I installed OS X and restored from backup, yet this time I did not restore the entire machine from backup and have not seen any problems. Perhaps there could be issue with some of the system files from previous drive?? I have no idea, just speculating..

This is all on a Unibody MB 2.4 GHz by the way.

My machine was brand new from Apple. So when I put the Vertex in, I just put all the software on from scratch. The problem popped up the first time before I ever migrated any of my data. So I took the bottom lid off, and checked to make sure the cable was on the drive right, and didn't think anything else of it, and proceded to migrate my data.

In hindsight, I should have put the standard drive back in, and migrated to that, sent the OCZ back, and waited for these issues to be ironed out by other people, rather than being a participant in the bleeding edge.

I thought these drives were leading edge. I didn't realize there were still bugs to be worked out.

[D111]

When you are switching technologies, with driver issues, registry issues, etc.. there is no such thing as a clean migration.

We can get it (most of the time) to work with clean installs.... but not clones... it is hit and miss.

It is not any more reasonable to expect a clean migration than to expect a bunch of sailors from a sailing ship moving to a steam ship to have a easy time adjusting!!!!

[D111]

I always recommend trailing edge technology for most applications.

[leonrolyat]

I've got Dual 2.26 Nahalem MacPro with Vertex 120 fw 1275
2 weeks no issues whatsoever with speed
no issues whatsoever with hibernation/wake up
I guess Im lucky

[harshw]

Pay attention. These are Mac issues we're talking about.
No drivers.
No registry.


:)

pay more attention - Mac has drivers. And Mac has a registry. People hack either to get things done. A majority of the Mac users are technically challenged and never understand that it is FreeBSD and Mach on the inside. But that doesn't change anything - it's an OS like Vista or Linux or FreeBSD and has drivers. And sometimes the drivers do cause conflicts. For example, jailbreaking the iPhone doesnt work properly on 10.5.5/10.5.6 and the only way out is to replace the USB driver - called IOUSBFamily.kext

[harshw]

I've got Dual 2.26 Nahalem MacPro with Vertex 120 fw 1275
2 weeks no issues whatsoever with speed
no issues whatsoever with hibernation/wake up
I guess Im lucky

IIRC on desktops hibernatemode is set to 0 and on laptops it is set to 3 by default.

Setting hibernatemode to 0 seems to solve the hibernation/wake from sleep issue with the Vertex. But there is still the issue of a random crash - it occurs randomly and seemingly with no pattern ... so it is tough to understand the cause of the crash

[jerry]

:)

pay more attention - Mac has drivers. And Mac has a registry. People hack either to get things done. A majority of the Mac users are technically challenged and never understand that it is FreeBSD and Mach on the inside. But that doesn't change anything - it's an OS like Vista or Linux or FreeBSD and has drivers. And sometimes the drivers do cause conflicts. For example, jailbreaking the iPhone doesnt work properly on 10.5.5/10.5.6 and the only way out is to replace the USB driver - called IOUSBFamily.kext

Yeah, all OSes have drivers of some sort. Even if they're embedded, (and the software touches the hardware directly... you still have to know how to do it!) Drivers are how modern OSes touch the hardware. But OS X ships with it's drivers since it only runs on hardware it was designed for. So there aren't a billion-billion combinations of drivers for hardware in OS X that can cause conflicts like other operating systems. The drivers that ship from Apple are all you will ever need. And unless a user is adding in special hardware not supported by Apple, Mac users aren't ever adding in drivers. Ever. I've been mucking around in OS X since it was Rhapsody, and the shell was the only way to get anything done. I've run it on production servers since 10.1. I've hacked it, I've compiled custom builds of BIND on it to run on it, to run ISP DNS servers. I've never seen a registry. I've connected OS X boxes to tape drives, SCSI raid arrays, cell phones, Bio-feedback sensors, tape libraries, various musical instruments, and other various non apple things that I can't even remember. I've never needed a driver yet. So that's what I base my driver comment on. The no drivers comment was based on the utter lack of 3rd party drivers in use on typical OS X system. I first ran Mach on a PowerPC back in 97. So I've been at this a while. But I don't, and will NEVER know it all. So teach me something new: tell me where the registry is on an OS X box.

[jerry]

Had a windows friend flash the drive on his last working windows machine (he's moved to Ubuntu on everything else) and the flash process to 1275 went smoothly. Did a fresh partition, and zeroed the drive, and formatted out a volume. Loaded the OS and all the apps, and my user sparsebundles, and got my lappy working again.

My first impression is that it *FEELS* faster. It feels snappier, even more so when there are multiple I/O things going on.

With 1197, any other IO on the system ground to a halt when doing a large I/O (copying multi GB image files). It was worse than a spinning platter hard drive. But with 1275 it's much better, and seems to actually be able to handle multiple I/O "threads" at once.

MacBench says it's faster too, in all but a couple of categories. One of them, Random Uncached reads of 4K blocks was MUCH lower in 1275. But others were somewhat better, and the overall score was 155.53 in 1275 vs of the prior score of 155.19 with 1197. To me, that's no change in overall score despite the drive being faster and slower in some categories. There's only so much you can do with hardware. Despite what MacBench says, the drive still *feels* faster and snappier.

I haven't had enough downtime to sleep the Mac to see what happens. Still in catch up mode from having an unavailalbe machine.

[BobF]

Yeah, all OSes have drivers of some sort. But OS X ships with it's drivers since it only runs on hardware it was designed for. So there aren't a billion-billion combinations of drivers for hardware in OS X that can cause conflicts like other operating systems. The drivers that ship from Apple are all you will ever need. And unless a user is adding in special hardware not supported by Apple, Mac users aren't ever adding in drivers. .

If you know all that, why are you mucking about trying to run hardware that OSX wasn't designed for?:scratch:

Just be patient and wait for Apple to catch up.

Bob F.

[D111]

If you know all that, why are you mucking about trying to run hardware that OSX wasn't designed for?:scratch:

Just be patient and wait for Apple to catch up.

Bob F.


Or, respect Apple's decision to not support this hardware and purchase only factory hardware from Apple.

They did a closed system and not support industry wide standards and interoperability for a reason.

[jerry]

After a night of sleep, the lappy woke up without incident this AM. If it lasts a week of sleeping and waking, I'll call the firmware upgrade to 1275 a cure to Mac unibodies not waking properly after sleep. Until then, I'll be making sure backups are running several times a day, and I'll be very carefull about not having anything saved before I sleep my mac.

[D111]

WHAT?! IT'S A HARD DRIVE!!! IT'S OS INDEPENDENT!!

Let me make sure I understand this... what you're implying by the above is that OCZs don't work in Macs because they're somehow specail and aren't hard drives? They don't conform to the SATA II spec? Are you saying that? For real?

Please tell me you're not saying that, because to do so would be incredibly stupid, and you don't strike me as an incredibly stupid person.


Solid State Drives built with MLC Chips and current generation controllers (Barefoot) are not Hard Drives.

It is not OS independent. It is a storage device that require its own OS/Application optimization that has not been done by any major OS house (not counting Linux) to date.

SATA II is strictly an interface standard, it does not deal with storage issues raised by SSDs.


Have I said it clearly enough?

[jgo]

They did a closed system and not support industry wide standards and interoperability for a reason.


I have used Apple computers for about 12 years now, and while there are many instances of proprietary restrictions to their products, I was unaware of any proprietary restrictions when it came to drives.

D111, what industry standard for drives does Apple fail to support?

[MBHockey]

I just experienced the sleep problem on my unibody MB with the 250 GB Vertex (1275). Came out of sleep this morning and i got beach balls everywhere (couldn't launch anything), so I had to do a hard reboot.

I had one lockup on the 1199 firmware. I think, both times, I put the machine to sleep via the menu item (in the upper left of the screen) rather than just putting the lid down and it had locked up upon waking. I'm not sure if this is just a coincidence, however.

Also, i have the default sleep mode set to "0" instead of "3". Is there any difference in how the machine sleeps if you choose sleep from the menu or just close the lid?

[jgo]

Also, i have the default sleep mode set to "0" instead of "3". Is there any difference in how the machine sleeps if you choose sleep from the menu or just close the lid?


Maybe try mode "1."

I found this in another forum:


To see what is your current mode, run this command:

$ pmset -g | grep hibernatemode

To switch to "hibernate" mode, run this command:

# sudo pmset -a hibernatemode 0

These are the modes that are supported:

# 0 - Old style sleep mode, with RAM powered on while sleeping, safe
sleep disabled, and super-fast wake.
# 1 - Hibernation mode, with RAM contents written to disk, system
totally shut down while “sleeping,” and slower wake up, due to reading
the contents of RAM off the hard drive.
# 3 - The default mode on machines introduced since about fall 2005.
RAM is powered on while sleeping, but RAM contents are also written to
disk before sleeping. In the event of total power loss, the system
enters hibernation mode automatically.
# 5 - This is the same as mode 1, but it’s for those using secure
virtual memory (in System Preferences -> Security).
# 7 - This is the same as mode 3, but it’s for those using secure
virtual memory.

[MBHockey]

Maybe try mode "1."

I found this in another forum:


To see what is your current mode, run this command:

$ pmset -g | grep hibernatemode

To switch to "hibernate" mode, run this command:

# sudo pmset -a hibernatemode 0

These are the modes that are supported:

# 0 - Old style sleep mode, with RAM powered on while sleeping, safe
sleep disabled, and super-fast wake.
# 1 - Hibernation mode, with RAM contents written to disk, system
totally shut down while “sleeping,” and slower wake up, due to reading
the contents of RAM off the hard drive.
# 3 - The default mode on machines introduced since about fall 2005.
RAM is powered on while sleeping, but RAM contents are also written to
disk before sleeping. In the event of total power loss, the system
enters hibernation mode automatically.
# 5 - This is the same as mode 1, but it’s for those using secure
virtual memory (in System Preferences -> Security).
# 7 - This is the same as mode 3, but it’s for those using secure
virtual memory.

That is of interest. The default sleep mode on my MacBook was 3 out of the box. However, by default, my computer was also using secure virtual memory. Why would it, then, not have a default sleep mode of 5 out of the box?

Could this be part of the problem?

[jgo]

That is of interest. The default sleep mode on my MacBook was 3 out of the box. However, by default, my computer was also using secure virtual memory. Why would it, then, not have a default sleep mode of 5 out of the box?


I just checked and my MBP is sleep/hibernate mode 3 AND secure memory is the default. Perhaps that part of the information regarding the modes is no longer correct.

My Vertex arrives any day now, and I simply want to know if one of the modes described is a reliable way to avoid the crashes.

[MBHockey]

I would like to know also. As far as I know, "0" is the recommended mode for the vertex.

[mikest]

Tony,

How do I get an RMA for my drive? It fails to show up on the bus intermittently and is frequently losing files (i.e., restart: files no longer there).

Thanks!

[joergr]

Joerg@Joerg- you have not posted in this thread. Here is your first post in another thread- http://www.ocztechnologyforum.com/forum/showthread.php?t=52568&page=9. Rob

my apologies!!!! mea culpa. just too sad about my vertex and my mac won´t function as i expected, so i lost the original thread. excuses.

[RyderOCZ]

Tony,

How do I get an RMA for my drive? It fails to show up on the bus intermittently and is frequently losing files (i.e., restart: files no longer there).

Thanks!Mike, did you flash the drive to 1275 firmware?

[jerry]

After flashing to 1275, my Mac again didn't wake from sleep this AM. I was tailing system.log and was able to stop the scrolling an type out some of the messages.

The reader's digest version pointed to the OS trying frantically to do disk I/O, that wasn't there.

IOBlockStorageDriver; executeRequest: request failed to start!

I would post more, but I fear my comments may be deleted much like my post to D1111 was deleted yesterday. -silently and without a trace-

My next course of action is to clone and pull the Vertex from my machine and replace it with a 7200 RPM drive. No amount of speed is worth data loss because a machine doesn't wake properly.

[harshw]

After flashing to 1275, my Mac again didn't wake from sleep this AM. I was tailing system.log and was able to stop the scrolling an type out some of the messages.

The reader's digest version pointed to the OS trying frantically to do disk I/O, that wasn't there.

IOBlockStorageDriver; executeRequest: request failed to start!

I would post more, but I fear my comments may be deleted much like my post to D1111 was deleted yesterday. -silently and without a trace-

My next course of action is to clone and pull the Vertex from my machine and replace it with a 7200 RPM drive. No amount of speed is worth data loss because a machine doesn't wake properly.

I'd have to say that this forum is a lot more tolerant than the discussion forums on Apple.

Sorry to hear about the drive though.

[MBHockey]

It seems Mac Pros were experiencing a similar wake from sleep issue:

http://discussions.apple.com/thread.jspa?threadID=1457979

There isn't a solution in there, but it's what comes up when I google:


IOBlockStorageDriver; executeRequest: request failed to start!

[MikhailT]

After flashing to 1275, my Mac again didn't wake from sleep this AM. I was tailing system.log and was able to stop the scrolling an type out some of the messages.

The reader's digest version pointed to the OS trying frantically to do disk I/O, that wasn't there.

IOBlockStorageDriver; executeRequest: request failed to start!

I would post more, but I fear my comments may be deleted much like my post to D1111 was deleted yesterday. -silently and without a trace-

My next course of action is to clone and pull the Vertex from my machine and replace it with a 7200 RPM drive. No amount of speed is worth data loss because a machine doesn't wake properly.

Was the message "resource" something after that executeRequest? We need a bit more info on that.

[jerry]

Was the message "resource" something after that executeRequest? We need a bit more info on that.

kernel[0]: t /] [Path /private/var/log/asl/StoreData] [FSLogMsgID 790305307 ] [FSLogMsgOrder Last]
kernel[0]: IOBlockStorageDriver [ IOBlockStorageDriver]; executeRequest: request failed to start!
kernel[0]: disk0s2: resource shortage.
kernel[0]:

.................

kernel[0]: IOBlockStorageDriver [ IOBlockStorageDriver]; executeRequest: request failed to start!
kernel[0]: disk0s2: resource shortage.
--- last message repeated 2 times---
com.appple.launchd[1] (com.apple.airportd[4062]): postix_spawmp("usr/libexec/airportd", ...): cannot allocate memory
com.apple.launchd[1] (com.apple.airportd[4062]): Exited with exiit code: 1

...................

Everything above, in a random order, repeating as fast as the window can scroll

[MikhailT]

It seems Mac Pros were experiencing a similar wake from sleep issue:

http://discussions.apple.com/thread.jspa?threadID=1457979

There isn't a solution in there, but it's what comes up when I google:


IOBlockStorageDriver; executeRequest: request failed to start!

Except in his case, it's the memory issue. I think he has a bad stick.

In our cases, the logs aren't pointing to the memory system but to the storage system.

If it is common wake from sleep issue, it would be far more visible than now on most people with MB/MBP, we aren't seeing that. What we're seeing is that most of the issues appear with Vertex SSDs.

[jerry]

Just to be complete, I'm running the firmware based Apple Hardware test. And it takes a long time. Hours. Since it is a new machine, I want to rule out any other problems, esp memory problems.

Only happens during wake after extended sleep, doesn't happen if a hibernate file is loaded in to RAM after long sleep.... memory allocation error in log.... It's plausible it could be a RAM issue. Sadly, the hardware tester doesn't doesn't test the RAM during sleep.

I should note that my machine has 4GB of ram, and has NEVER done a pageout yet. It's never had enough uptime or apps running to get anywhere near low on RAM yet. I could see the "memory allocation" problems being connected to a hard drive I/O problem, due to the fact that virtual memory doesn't like it when its page file isn't accessable for any reason. If the VM file can't be accessed, I'd assume that the VM system would just hang the machine. That's the theory I was operating under before.

So I'm going to rule out any possible RAM problem before I finally decide it's an SSD drive issue. The fact that I was crashing after every sleep longer than 4 hours with 1199 firmware, and only sometimes after long sleeps with 1275 still could just be a coincidence. I really want this SSD to work.

[harshw]

Just to be complete, I'm running the firmware based Apple Hardware test. And it takes a long time. Hours. Since it is a new machine, I want to rule out any other problems, esp memory problems.

Only happens during wake after extended sleep, doesn't happen if a hibernate file is loaded in to RAM after long sleep.... memory allocation error in log.... It's plausible it could be a RAM issue. Sadly, the hardware tester doesn't doesn't test the RAM during sleep.

I should note that my machine has 4GB of ram, and has NEVER done a pageout yet. It's never had enough uptime or apps running to get anywhere near low on RAM yet. I could see the "memory allocation" problems being connected to a hard drive I/O problem, due to the fact that virtual memory doesn't like it when its page file isn't accessable for any reason. If the VM file can't be accessed, I'd assume that the VM system would just hang the machine. That's the theory I was operating under before.

So I'm going to rule out any possible RAM problem before I finally decide it's an SSD drive issue. The fact that I was crashing after every sleep longer than 4 hours with 1199 firmware, and only sometimes after long sleeps with 1275 still could just be a coincidence. I really want this SSD to work.

But this is the price one pays for bleeding edge :D And of course once you put a SSD in the Macbook - there is no way you will want to go back to the HDD again.

Anyways, I dont think it is the RAM. My MacBook has 4GB of Apple branded RAM. It never had a crash with the 5400 rpm and 7200 rpm HDDs. Also, it's not the GPU and it's not the wake from RAM itself. I have tried with mode 0 and mode 3, I have never had a crash immediately from wake but always had a crash randomly - I dont switch off the machine, I usually close the lid and let it sleep. The problem isnt heavy disk activity or heavy network activity. The crashes are totally random.

The problem is the SATA/AHCI drivers assumes they are going to be connected to a HDD. The fact that it is a SSD on the other side means a lot of assumptions are way off. I've seen some really funky errors with RAID cards and SSDs due to timing - HDDs have latency and most driver code uses the latency very cleverly, SSDs have latency that is 10x to 100x lower and can wreak havoc with code loops in RAID card firmware. So this may be either something with the AHCI driver or then something with the Vertex firmware. Or it could be with the way the NCQ stuff works since it works differently on SSDs v/s HDDs. Or even something to do with the way the SMART code interacts with the OS.

I really think it would be nice if OCZ can give us a debug variant of the firmware that recorded the last x commands sent to the drive where x=65,536 or something. That would enable us to debug very precisely, since the OS logs themselves are not going to record anything ...

[MBHockey]

But this is the price one pays for bleeding edge :D And of course once you put a SSD in the Macbook - there is no way you will want to go back to the HDD again.

Anyways, I dont think it is the RAM. My MacBook has 4GB of Apple branded RAM. It never had a crash with the 5400 rpm and 7200 rpm HDDs. Also, it's not the GPU and it's not the wake from RAM itself. I have tried with mode 0 and mode 3, I have never had a crash immediately from wake but always had a crash randomly - I dont switch off the machine, I usually close the lid and let it sleep. The problem isnt heavy disk activity or heavy network activity. The crashes are totally random.

The problem is the SATA/AHCI drivers assumes they are going to be connected to a HDD. The fact that it is a SSD on the other side means a lot of assumptions are way off. I've seen some really funky errors with RAID cards and SSDs due to timing - HDDs have latency and most driver code uses the latency very cleverly, SSDs have latency that is 10x to 100x lower and can wreak havoc with code loops in RAID card firmware. So this may be either something with the AHCI driver or then something with the Vertex firmware. Or it could be with the way the NCQ stuff works since it works differently on SSDs v/s HDDs. Or even something to do with the way the SMART code interacts with the OS.

I really think it would be nice if OCZ can give us a debug variant of the firmware that recorded the last x commands sent to the drive where x=65,536 or something. That would enable us to debug very precisely, since the OS logs themselves are not going to record anything ...

I was hoping they were doing something along these lines internally. I really don't want to RMA the drive, because it's great when it works (which is most of the time), but I don't want to pay such a high premium for something that is unstable. I'm most likely going to RMA the drive by the end of April if we don't hear anything about this issue since my return window will be done.

[jerry]

But this is the price one pays for bleeding edge :D And of course once you put a SSD in the Macbook - there is no way you will want to go back to the HDD again.


I didn't think these were bleeding edge. I am not a fan of bleeding edge. My computers are tools. They are what I use to make a living. I can't afford bleeding edge. My customers will leave me and my income will vanish if I use bleeding edge. SSDs have been around for a few years now, and are on their way to going mainstream. OCZ has years of SSD development/sales. I simply thought I'd go 3rd party (OCZ) rather than pay the "apple tax" for a smaller, more expensive, slower Apple SSD. I wasn't hot-rodding my Mac, it's pure stock, except for the hard drive that they make very easy for the user to replace.

I don't mind slow. My last laptop is 1.3Ghz G4 with a 5400 RPM drive. Plenty fast. But more importantly, incredibly reliable. I only rebooted a few times a year, with uptimes usually between 90 and 180 days at reboot time.

[jerry]

Extended memory tests came out fine. I'm currently trying the cold soak test that involves my freezer.

Since the problem only shows itself -in my case- after an extended sleep, a couple of things could be happening. It could be electrical. For example, ram not staying refreshed during sleep or a capacitor being fully discharged in the SSD that needs time to charge up before the SSD is ready. Or it could be thermal.

So I'm using the freezer test to try and accelerate the normal several hour cool down of the machine. So far, doing my limited testing with my lappy and an infrared thermometer, I've only uncovered that the CPU temp probe's minimum temp is 50 degrees F, and that the coldest spot in my freezer reads -8 degrees F. I haven't been able to reproduce any crashes or wake from sleep hangs.

I feel like I'm in my own episode of Myth Busters.

[Tony]

We have a FW update coming that does address some mac sleep and hibernation issues.

I would consider flashing this when i get the go ahead to release.

[MBHockey]

We have a FW update coming that does address some mac sleep and hibernation issues.

I would consider flashing this when i get the go ahead to release.

That's wonderful news. I can't wait to give it a shot.

Got my jumper and BartPE disc ready and waiting... ;)

[MikhailT]

We have a FW update coming that does address some mac sleep and hibernation issues.

I would consider flashing this when i get the go ahead to release.


You are going to make a lot of mac users happy if this works.

Please do keep us informed of the progress.


As for people misunderstanding my RAM/Storage post, I did not mean Jerry has a RAM problem. I was talking about the guy in the apple's board who had the wake from sleep issue, his case involved memory issue while Jerry and whoever posted the "resource shortage" is having an issue with the storage system. It is possible RAM is involved since depending on the hibernation mode, RAM has some effects toward the storage system. It doesn't hurt to rule out the RAM first tho.

[MBHockey]

Is anyone else getting random Spotlight crashes too?

It's happened a bit more than the whole system hangups that happen after sleep. On average once a day or so. It's quite brief, and doesn't take down the whole system, but it definitely wasn't happening prior to the Vertex.

This is the most recent one's crash log:


Process: Spotlight [143]
Path: /System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight
Identifier: com.apple.spotlight
Version: 10.5 (398.25)
Build Info: Spotlight-3982500~1
Code Type: X86 (Native)
Parent Process: launchd [84]

Date/Time: 2009-04-07 16:12:13.941 -0400
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c1c7e2bb
Crashed Thread: 2

Thread 0:
0 libSystem.B.dylib 0x021a11c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x021a89bc mach_msg + 72
2 com.apple.CoreGraphics 0x03e5ede8 _CGSOrderSurface + 139
3 com.apple.AppKit 0x00dc981f -[NSSurface orderSurface:relativeTo:] + 388
4 com.apple.AppKit 0x00e12792 -[NSSurface orderOut] + 50
5 com.apple.AppKit 0x00dc855b -[NSSurface setFrame:] + 133
6 com.apple.AppKit 0x00dc8475 -[NSSurface syncToViewUnconditionally] + 254
7 com.apple.AppKit 0x00d62bf6 -[NSView _invalidateGStatesForTree] + 499
8 com.apple.AppKit 0x00d629b7 -[NSView _invalidateFocus] + 35
9 com.apple.AppKit 0x00d6292a -[NSView setFrameOrigin:] + 513
10 com.apple.AppKit 0x00ec8cad -[NSProgressIndicator setFrameOrigin:] + 226
11 com.apple.AppKit 0x00d68a39 -[NSView setFrame:] + 197
12 com.apple.spotlight 0x0001d9ae 0x1000 + 117166
13 com.apple.spotlight 0x000182d5 0x1000 + 94933
14 com.apple.Foundation 0x003e2e1a _nsnote_callback + 106
15 com.apple.CoreFoundation 0x0253c8da __CFXNotificationPost + 362
16 com.apple.CoreFoundation 0x0253cbb3 _CFXNotificationPostNotification + 179
17 com.apple.Foundation 0x0041035c -[NSNotificationCenter postNotification:] + 124
18 com.apple.Foundation 0x003e439c __NSThreadPerformPerform + 476
19 com.apple.CoreFoundation 0x0255b5f5 CFRunLoopRunSpecific + 3141
20 com.apple.CoreFoundation 0x0255bcd8 CFRunLoopRunInMode + 88
21 com.apple.HIToolbox 0x02b3f2c0 RunCurrentEventLoopInMode + 283
22 com.apple.HIToolbox 0x02b3f0d9 ReceiveNextEventCommon + 374
23 com.apple.HIToolbox 0x02b3ef4d BlockUntilNextEventMatchingListInMode + 106
24 com.apple.AppKit 0x00d7fd7d _DPSNextEvent + 657
25 com.apple.AppKit 0x00d7f630 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
26 com.apple.AppKit 0x00d7866b -[NSApplication run] + 795
27 com.apple.AppKit 0x00d458a4 NSApplicationMain + 574
28 com.apple.spotlight 0x0000276e 0x1000 + 5998

Thread 1:
0 libSystem.B.dylib 0x021a83ae __semwait_signal + 10
1 libSystem.B.dylib 0x021d2d0d pthread_cond_wait$UNIX2003 + 73
2 com.apple.QuartzCore 0x0311aab9 fe_fragment_thread + 54
3 libSystem.B.dylib 0x021d2095 _pthread_start + 321
4 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 2 Crashed:
0 libobjc.A.dylib 0x023ab688 objc_msgSend + 24
1 com.apple.spotlight 0x0000f159 0x1000 + 57689
2 com.apple.spotlight 0x0000d662 0x1000 + 50786
3 com.apple.spotlight 0x0000b45e 0x1000 + 42078
4 com.apple.spotlight 0x000364c4 0x1000 + 218308
5 com.apple.Foundation 0x00474064 -[NSOperation start] + 772
6 com.apple.Foundation 0x00473d52 __runop + 34
7 libSystem.B.dylib 0x0220a40f _pthread_wqthread + 331
8 libSystem.B.dylib 0x0220a2c2 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x0220a292 __workq_ops + 10
1 libSystem.B.dylib 0x0220a2c2 start_wqthread + 30

Thread 4:
0 libSystem.B.dylib 0x021a11c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x021a89bc mach_msg + 72
2 com.apple.CoreFoundation 0x0255b0ae CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x0255bcd8 CFRunLoopRunInMode + 88
4 com.apple.spotlight 0x000336ce 0x1000 + 206542
5 com.apple.Foundation 0x003e37ed -[NSThread main] + 45
6 com.apple.Foundation 0x003e3394 __NSThread__main__ + 308
7 libSystem.B.dylib 0x021d2095 _pthread_start + 321
8 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x021a83ae __semwait_signal + 10
1 libSystem.B.dylib 0x021a8176 usleep$UNIX2003 + 61
2 com.apple.AppKit 0x00de6299 -[NSUIHeartBeat _heartBeatThread:] + 2042
3 com.apple.Foundation 0x003e37ed -[NSThread main] + 45
4 com.apple.Foundation 0x003e3394 __NSThread__main__ + 308
5 libSystem.B.dylib 0x021d2095 _pthread_start + 321
6 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 2 crashed with X86 Thread State (32-bit):
eax: 0x1f750980 ebx: 0xb0122a9c ecx: 0x0244a748 edx: 0xc1c7e29b
edi: 0x1f7f7d30 esi: 0x1f7f7d30 ebp: 0xb0122b08 esp: 0xb01229f8
ss: 0x0000001f efl: 0x00010202 eip: 0x023ab688 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0xc1c7e2bb

Binary Images:
0x1000 - 0x43fff com.apple.spotlight 10.5 (398.25) <c75851bec473eb02543a75ebb651996d> /System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight
0x57000 - 0x57ff8 com.apple.ApplicationServices 34 (34) <ee7bdf593da050bb30c7a1fc446eb8a6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x5f000 - 0x68fff com.apple.framework.calculate 1.3.0 (8) /System/Library/PrivateFrameworks/Calculate.framework/Versions/A/Calculate
0x70000 - 0x70fff com.apple.Carbon 136 (136) <4177916bbf70e0ddc446f94001d54c95> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x74000 - 0x74ffa com.apple.CoreServices 32 (32) <373d6a888f9204641f313bc6070ae065> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7c000 - 0x84fff com.apple.DiskArbitration 2.2.1 (2.2.1) <2664eeb3a4d0c95a21c089892a0ae8d0> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x8e000 - 0x8effe com.apple.quartzframework 1.5 (1.5) <6865aa0aeaa584b5a54d43f2f21d6c08> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x92000 - 0x97fff com.apple.backup.framework 1.0 (1.0) /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0xa1000 - 0xaefe7 com.apple.opengl 1.5.9 (1.5.9) <7e5048a2677b41098c84045305f42f7f> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x131000 - 0x1e8ff3 com.apple.QTKit 7.6 (1290) /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x262000 - 0x26cffe com.apple.URLMount 3.1.1 (3.1.1) <a6aece1c9c34992e08acf4b68e523f90> /System/Library/PrivateFrameworks/URLMount.framework/Versions/A/URLMount
0x274000 - 0x274ffc com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x3d9000 - 0x654fe7 com.apple.Foundation 6.5.7 (677.22) <8fe77b5d15ecdae1240b4cb604fc6d0b> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7b2000 - 0x7cfff7 com.apple.QuickLookFramework 1.3.1 (170.9) /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7e3000 - 0x7eafe9 libgcc_s.1.dylib ??? (???) <e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
0x7f0000 - 0x7f4fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x7f8000 - 0x7f8ffd com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0xd3f000 - 0x153dfef com.apple.AppKit 6.5.6 (949.43) <a3a300499bbe4f1dfebf71d752d01916> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x1a7e000 - 0x1ab5fff com.apple.SystemConfiguration 1.9.2 (1.9.2) <eab546255ac099b9616df999c9359d0e> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x1ad4000 - 0x1df9fe2 com.apple.QuickTime 7.6.0 (1290) <bc0920abbbaad03f5513ac7ffbd30633> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x1ebf000 - 0x203efff com.apple.AddressBook.framework 4.1.1 (699) <60ddae72a1df8ddbc5c53df92f372b76> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x211a000 - 0x2169fff com.apple.QuickLookUIFramework 1.3.1 (170.9) /System/Library/PrivateFrameworks/QuickLookUI.framework/Versions/A/QuickLookUI
0x21a0000 - 0x2307ff3 libSystem.B.dylib ??? (???) <d68880dfb1f8becdbdac6928db1510fb> /usr/lib/libSystem.B.dylib
0x2396000 - 0x2476fff libobjc.A.dylib ??? (???) <400e943f9e8a678eea22a1d1205490ee> /usr/lib/libobjc.A.dylib
0x24e8000 - 0x261bfff com.apple.CoreFoundation 6.5.5 (476.17) <4a70c8dbb582118e31412c53dc1f407f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x2713000 - 0x2865ff3 com.apple.audio.toolbox.AudioToolbox 1.5.2 (1.5.2) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x28da000 - 0x29bfff3 com.apple.CoreData 100.1 (186) <50219bcb005cb15ea999a19391a8d523> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x2a3a000 - 0x2ac4fef com.apple.DesktopServices 1.4.7 (1.4.7) <c64f04641052fdaa0f0cdee3564a0fd3> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x2b0f000 - 0x2e17fff com.apple.HIToolbox 1.5.4 (???) <3747086ba21ee419708a5cab946c8ba6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x2f75000 - 0x3000fff com.apple.framework.IOKit 1.5.1 (???) <f9f5f0d070e197a832d86751e1d44545> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x3026000 - 0x33c3fef com.apple.QuartzCore 1.5.7 (1.5.7) <2fed2dd7565c84a0f0c608d41d4d172c> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x34bd000 - 0x368bff3 com.apple.security 5.0.4 (34102) <55dda7486df4e8e1d61505be16f83a1c> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x37d0000 - 0x37d9fff com.apple.speech.recognition.framework 3.7.24 (3.7.24) <da2d8411921a3fd8bc898dc753b7f3ee> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x37e3000 - 0x380efe7 libauto.dylib ??? (???) <2e44c523b851e8e25f05d13a48070a58> /usr/lib/libauto.dylib
0x381c000 - 0x3954ff7 libicucore.A.dylib ??? (???) <18098dcf431603fe47ee027a60006c85> /usr/lib/libicucore.A.dylib
0x39a8000 - 0x3a89ff7 libxml2.2.dylib ??? (???) <306036e0070330e35045650e6d9f0d05> /usr/lib/libxml2.2.dylib
0x3ab6000 - 0x3ac4ffd libz.1.dylib ??? (???) <a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
0x3aca000 - 0x3b04fe7 com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x3b24000 - 0x3ba1feb com.apple.audio.CoreAudio 3.1.1 (3.1.1) <f35477a5e23db0fa43233c37da01ae1c> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x3bf6000 - 0x3c89ff3 com.apple.ApplicationServices.ATS 3.4 (???) <8c51de0ec3deaef416578cd59df38754> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x3cb0000 - 0x3d7bfff com.apple.ColorSync 4.5.1 (4.5.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x3dbc000 - 0x445cfff com.apple.CoreGraphics 1.407.2 (???) <3a91d1037afde01d1d8acdf9cd1caa14> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x452c000 - 0x4586ff7 com.apple.CoreText 2.0.4 (???) <f9a90116ae34a2b0d84e87734766fb3a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x45c6000 - 0x4617ff7 com.apple.HIServices 1.7.0 (???) <01b690d1f376e400ac873105533e39eb> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x4641000 - 0x4787ff7 com.apple.ImageIO.framework 2.0.4 (2.0.4) <b407f06ff9b6893899e2e399cb65c953> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x47df000 - 0x47efffc com.apple.LangAnalysis 1.6.4 (1.6.4) <bc7eb703ddc37bf85adf93e35efd3947> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x47fc000 - 0x48a3feb com.apple.QD 3.11.54 (???) <c31150b40fcc27c195de40f0ae138666> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x48cc000 - 0x48dcfff com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <273d96ff861dc68be659c07ef56f599a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x48eb000 - 0x4bc5ff3 com.apple.CoreServices.CarbonCore 786.11 (786.11) <f06fe5d92d56ac5aa52d1ba182745924> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x4c2f000 - 0x4cccfe4 com.apple.CFNetwork 422.15.2 (422.15.2) <80851410a5592b7c3b149b2ff849bcc1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x4d44000 - 0x4d8dfef com.apple.Metadata 10.5.2 (398.25) <e0572f20350523116f23000676122a8d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x4da9000 - 0x4e63fe3 com.apple.CoreServices.OSServices 226.5 (226.5) <ef9945b1304495f3e8085c935f1b81e3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x4ec8000 - 0x4f47ff5 com.apple.SearchKit 1.2.1 (1.2.1) <f28f8dd0f155a6453411a0c9b5702764> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x4f8a000 - 0x4fb9fe3 com.apple.AE 402.3 (402.3) <4cb9ef65cf116d6dd424f0ce98c2d015> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x4fd1000 - 0x505dff7 com.apple.LaunchServices 290.3 (290.3) <6f9629f4ed1ba3bb313548e6838b2888> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x50a3000 - 0x50b9fff com.apple.DictionaryServices 1.0.0 (1.0.0) <7d20b8d1fb238c3e71d0fa6fda18c4f7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x50cb000 - 0x50d2ffe libbsm.dylib ??? (???) <fa7ae5f1a621d9b69e7e18747c9405fb> /usr/lib/libbsm.dylib
0x50d9000 - 0x5136ffb libstdc++.6.dylib ??? (???) <f75e5133d72769de5ce6c06153fc65f6> /usr/lib/libstdc++.6.dylib
0x5187000 - 0x520eff7 libsqlite3.0.dylib ??? (???) <eeedc8bf6881ac9f2c1954b1c8037720> /usr/lib/libsqlite3.0.dylib
0x521b000 - 0x523ffff libxslt.1.dylib ??? (???) <0a9778d6368ae668826f446878deb99b> /usr/lib/libxslt.1.dylib
0x5249000 - 0x52fbffb libcrypto.0.9.7.dylib ??? (???) <75b80bff0d5cfaf10b6b6fe982da3578> /usr/lib/libcrypto.0.9.7.dylib
0x534a000 - 0x5411ff2 com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x5421000 - 0x5421ffd com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x5425000 - 0x54a2fef libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x54b0000 - 0x54ddfeb libvDSP.dylib ??? (???) <4daafed78a471133ec30b3ae634b6d3e> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x54e9000 - 0x58f9fef libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x593f000 - 0x5cfdfea libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x5d33000 - 0x5d52ffa libJPEG.dylib ??? (???) <b822342bcc764c83d4557a8b67fa0c1c> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x5d5a000 - 0x5d99fef libTIFF.dylib ??? (???) <d4bcc9b9c508e53849d2d46bb6900922> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x5da4000 - 0x5da8fff libGIF.dylib ??? (???) <7714ae24eb64b48fa719fb99bcbe34f3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x5dae000 - 0x5dc9ffb libPng.dylib ??? (???) <0d6b991afc831ea06f2958e5933d33dd> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x5dd1000 - 0x5dd3ff5 libRadiance.dylib ??? (???) <82d606c49f5dc77231f9d0e2be9ed6ab> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x5dd8000 - 0x5e00fff libcups.2.dylib ??? (???) <16bec7c6a004f744804e2281a1b1c094> /usr/lib/libcups.2.dylib
0x5e0b000 - 0x5e29fff libresolv.9.dylib ??? (???) <9ed809256ce8913cddc3269c2e364654> /usr/lib/libresolv.9.dylib
0x5e33000 - 0x5e33ffd com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x5e37000 - 0x5e37ffb com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x5e3b000 - 0x5e45feb com.apple.audio.SoundManager 3.9.2 (3.9.2) <df077a8048afc3075c6f2d9e7780e78e> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x5e4e000 - 0x5e8cff7 libGLImage.dylib ??? (???) <1123b8a48bcbe9cc7aa8dd8e1a214a66> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x5e96000 - 0x5e97ffc libffi.dylib ??? (???) <eaf10b99a3fbc4920b175809407466c0> /usr/lib/libffi.dylib
0x5e9c000 - 0x5eb4ff7 com.apple.CoreVideo 1.6.0 (20.0) <c0d869876af51283a160cd2224a23abf> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x5ec8000 - 0x5f21ff7 libGLU.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x5f35000 - 0x5f41ffe libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x5f4f000 - 0x6420f3e libGLProgrammability.dylib ??? (???) <5d283543ac844e7c6fa3440ac56cd265> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x654d000 - 0x6552fff com.apple.CommonPanels 1.2.4 (85) <c135f02edd6b2e2864311e0b9d08a98d> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x655b000 - 0x655efff com.apple.help 1.1 (36) <1a25a8fbb49a830efb31d5c0a52939cd> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x6564000 - 0x65c0ff7 com.apple.htmlrendering 68 (1.1.3) <1c5c0c417891b920dfe139385fc6c155> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x65ee000 - 0x6603ffb com.apple.ImageCapture 5.0.1 (5.0.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x661e000 - 0x66b1fff com.apple.ink.framework 101.3 (86) <d4c85b5cafa8027fff042b84a8be71dc> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x66d0000 - 0x6712fef com.apple.NavigationServices 3.5.2 (163) <72cdc9d21f6690837870923e7b8ca358> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x6740000 - 0x6758fff com.apple.openscripting 1.2.8 (???) <0129d2f750f5ddcb92f4acf8a3541952> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x676a000 - 0x676cfff com.apple.securityhi 3.0 (30817) <40562b85d99118354c974e76c32fa6fb> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x6772000 - 0x679bfff com.apple.CoreMediaPrivate 15.0 (15.0) /System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CoreMediaPrivate
0x67ae000 - 0x67edfff com.apple.CoreMediaIOServicesPrivate 15.0 (15.0) /System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/CoreMediaIOServicesPrivate
0x6815000 - 0x6815ff8 com.apple.Cocoa 6.5 (???) <a1bc9247cf65c20f1a44d0973cbe649c> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x6819000 - 0x69d5ff3 com.apple.QuartzComposer 2.1 (106.13) <40f034e8c8fd31c9081f5283dcf22b78> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
0x6aec000 - 0x6b5efff com.apple.PDFKit 2.1.2 (2.1.2) /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit
0x6ba5000 - 0x6bd6ffb com.apple.quartzfilters 1.5.0 (1.5.0) <92b4f39479fdcabae0d8f53febd22fad> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters
0x6bfe000 - 0x6d36fe7 com.apple.imageKit 1.0.2 (1.0) <2e354566521df8b1e3a78e9aeab5e6b4> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
0x6e03000 - 0x6f68fe7 com.apple.JavaScriptCore 5528 (5528.15) <a1edf2b00622f9d833987cb333b432ac> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x6fbc000 - 0x6fcbffe com.apple.DSObjCWrappers.Framework 1.3 (1.3) <182986b74247b459b2a67a47071bdc6b> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers
0x6fd9000 - 0x6fdefff com.apple.DisplayServicesFW 2.0.2 (2.0.2) <97878a73074e7da4fe31ea010a5d5ae1> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices
0x6fe7000 - 0x7005ff3 com.apple.DirectoryService.Framework 3.5.5 (3.5.5) <f8931f64103c8a86b82e9714352f4323> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x7012000 - 0x7012ffe com.apple.MonitorPanelFramework 1.2.0 (1.2.0) <1f4c10fcc17187a6f106e0a0be8236b0> /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPanel
0x7018000 - 0x704afff com.apple.LDAPFramework 1.4.5 (110) <e9e44dec1fd4b049276257c7cc97b423> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7055000 - 0x7064fff libsasl2.2.dylib ??? (???) <bb7971ca2f609c070f87786a93d1041e> /usr/lib/libsasl2.2.dylib
0x706c000 - 0x7090feb libssl.0.9.7.dylib ??? (???) <d04156c610530ca44979c899834fc24d> /usr/lib/libssl.0.9.7.dylib
0x70b9000 - 0x70c5ffb +com.fsb.SafariBlock ??? (2.2r1) <fe7dd96f3e475128f5b951956f41f1c9> /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock
0x7300000 - 0x730bfe7 libCSync.A.dylib ??? (???) <e6aceed359bd228f42bc1246af5919c9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x7314000 - 0x733cff7 com.apple.shortcut 1 (1.0) <35cd17d0179ca839c5fb08694f3dc5ef> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x735b000 - 0x7367ff9 com.apple.helpdata 1.0.1 (14.2) /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7376000 - 0x73b7fe7 libRIP.A.dylib ??? (???) <5d0b5af7992e14de017f9a9c7cb05960> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x73f0000 - 0x73f5ff3 libCGXCoreImage.A.dylib ??? (???) <375e0cdb64b043378dbf637992bbfeb0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
0x7589000 - 0x758efff com.apple.DictionaryServiceComponent 1.1 (1.1) <0c718fcdccb0e50ce699cb46073b5b88> /System/Library/Components/DictionaryService.component/Contents/MacOS/DictionaryService
0x76e2000 - 0x76e9ff7 libCGATS.A.dylib ??? (???) <386dce4b28448fb86e33e06ac466f4d8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x189c5000 - 0x18bbdfff com.apple.RawCamera.bundle 2.0.13 (435) <083354ccec68bf7c9fc99523a5838f92> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x1cf5d000 - 0x1d14ffea +com.elgato.mpegsupport EyeTV MPEG Support 1.0.7 (build 43) (1.0.7) /Library/QuickTime/EyeTV MPEG Support.component/Contents/MacOS/EyeTV MPEG Support
0x20000000 - 0x200b0fff edu.mit.Kerberos 6.0.12 (6.0.12) <685cc018c133668d0d3ac6a1cb63cff9> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x64b00000 - 0x64b06fff com.apple.print.framework.Print 218.0.2 (220.1) <6c2ddea45d9cdff9a9be0666a13e2dd4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
0xfa100000 - 0xfa17aff8 com.apple.print.framework.PrintCore 5.5.3 (245.3) <98633ef67d419c1b02f56556cb4d843d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

[harshw]

Is anyone else getting random Spotlight crashes too?

It's happened a bit more than the whole system hangups that happen after sleep. On average once a day or so. It's quite brief, and doesn't take down the whole system, but it definitely wasn't happening prior to the Vertex.

This is the most recent one's crash log:


Process: Spotlight [143]
Path: /System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight
Identifier: com.apple.spotlight
Version: 10.5 (398.25)
Build Info: Spotlight-3982500~1
Code Type: X86 (Native)
Parent Process: launchd [84]

Date/Time: 2009-04-07 16:12:13.941 -0400
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c1c7e2bb
Crashed Thread: 2

Thread 0:
0 libSystem.B.dylib 0x021a11c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x021a89bc mach_msg + 72
2 com.apple.CoreGraphics 0x03e5ede8 _CGSOrderSurface + 139
3 com.apple.AppKit 0x00dc981f -[NSSurface orderSurface:relativeTo:] + 388
4 com.apple.AppKit 0x00e12792 -[NSSurface orderOut] + 50
5 com.apple.AppKit 0x00dc855b -[NSSurface setFrame:] + 133
6 com.apple.AppKit 0x00dc8475 -[NSSurface syncToViewUnconditionally] + 254
7 com.apple.AppKit 0x00d62bf6 -[NSView _invalidateGStatesForTree] + 499
8 com.apple.AppKit 0x00d629b7 -[NSView _invalidateFocus] + 35
9 com.apple.AppKit 0x00d6292a -[NSView setFrameOrigin:] + 513
10 com.apple.AppKit 0x00ec8cad -[NSProgressIndicator setFrameOrigin:] + 226
11 com.apple.AppKit 0x00d68a39 -[NSView setFrame:] + 197
12 com.apple.spotlight 0x0001d9ae 0x1000 + 117166
13 com.apple.spotlight 0x000182d5 0x1000 + 94933
14 com.apple.Foundation 0x003e2e1a _nsnote_callback + 106
15 com.apple.CoreFoundation 0x0253c8da __CFXNotificationPost + 362
16 com.apple.CoreFoundation 0x0253cbb3 _CFXNotificationPostNotification + 179
17 com.apple.Foundation 0x0041035c -[NSNotificationCenter postNotification:] + 124
18 com.apple.Foundation 0x003e439c __NSThreadPerformPerform + 476
19 com.apple.CoreFoundation 0x0255b5f5 CFRunLoopRunSpecific + 3141
20 com.apple.CoreFoundation 0x0255bcd8 CFRunLoopRunInMode + 88
21 com.apple.HIToolbox 0x02b3f2c0 RunCurrentEventLoopInMode + 283
22 com.apple.HIToolbox 0x02b3f0d9 ReceiveNextEventCommon + 374
23 com.apple.HIToolbox 0x02b3ef4d BlockUntilNextEventMatchingListInMode + 106
24 com.apple.AppKit 0x00d7fd7d _DPSNextEvent + 657
25 com.apple.AppKit 0x00d7f630 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
26 com.apple.AppKit 0x00d7866b -[NSApplication run] + 795
27 com.apple.AppKit 0x00d458a4 NSApplicationMain + 574
28 com.apple.spotlight 0x0000276e 0x1000 + 5998

Thread 1:
0 libSystem.B.dylib 0x021a83ae __semwait_signal + 10
1 libSystem.B.dylib 0x021d2d0d pthread_cond_wait$UNIX2003 + 73
2 com.apple.QuartzCore 0x0311aab9 fe_fragment_thread + 54
3 libSystem.B.dylib 0x021d2095 _pthread_start + 321
4 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 2 Crashed:
0 libobjc.A.dylib 0x023ab688 objc_msgSend + 24
1 com.apple.spotlight 0x0000f159 0x1000 + 57689
2 com.apple.spotlight 0x0000d662 0x1000 + 50786
3 com.apple.spotlight 0x0000b45e 0x1000 + 42078
4 com.apple.spotlight 0x000364c4 0x1000 + 218308
5 com.apple.Foundation 0x00474064 -[NSOperation start] + 772
6 com.apple.Foundation 0x00473d52 __runop + 34
7 libSystem.B.dylib 0x0220a40f _pthread_wqthread + 331
8 libSystem.B.dylib 0x0220a2c2 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x0220a292 __workq_ops + 10
1 libSystem.B.dylib 0x0220a2c2 start_wqthread + 30

Thread 4:
0 libSystem.B.dylib 0x021a11c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x021a89bc mach_msg + 72
2 com.apple.CoreFoundation 0x0255b0ae CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x0255bcd8 CFRunLoopRunInMode + 88
4 com.apple.spotlight 0x000336ce 0x1000 + 206542
5 com.apple.Foundation 0x003e37ed -[NSThread main] + 45
6 com.apple.Foundation 0x003e3394 __NSThread__main__ + 308
7 libSystem.B.dylib 0x021d2095 _pthread_start + 321
8 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x021a83ae __semwait_signal + 10
1 libSystem.B.dylib 0x021a8176 usleep$UNIX2003 + 61
2 com.apple.AppKit 0x00de6299 -[NSUIHeartBeat _heartBeatThread:] + 2042
3 com.apple.Foundation 0x003e37ed -[NSThread main] + 45
4 com.apple.Foundation 0x003e3394 __NSThread__main__ + 308
5 libSystem.B.dylib 0x021d2095 _pthread_start + 321
6 libSystem.B.dylib 0x021d1f52 thread_start + 34

Thread 2 crashed with X86 Thread State (32-bit):
eax: 0x1f750980 ebx: 0xb0122a9c ecx: 0x0244a748 edx: 0xc1c7e29b
edi: 0x1f7f7d30 esi: 0x1f7f7d30 ebp: 0xb0122b08 esp: 0xb01229f8
ss: 0x0000001f efl: 0x00010202 eip: 0x023ab688 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0xc1c7e2bb

Binary Images:
0x1000 - 0x43fff com.apple.spotlight 10.5 (398.25) <c75851bec473eb02543a75ebb651996d> /System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight
0x57000 - 0x57ff8 com.apple.ApplicationServices 34 (34) <ee7bdf593da050bb30c7a1fc446eb8a6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x5f000 - 0x68fff com.apple.framework.calculate 1.3.0 (8) /System/Library/PrivateFrameworks/Calculate.framework/Versions/A/Calculate
0x70000 - 0x70fff com.apple.Carbon 136 (136) <4177916bbf70e0ddc446f94001d54c95> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x74000 - 0x74ffa com.apple.CoreServices 32 (32) <373d6a888f9204641f313bc6070ae065> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7c000 - 0x84fff com.apple.DiskArbitration 2.2.1 (2.2.1) <2664eeb3a4d0c95a21c089892a0ae8d0> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x8e000 - 0x8effe com.apple.quartzframework 1.5 (1.5) <6865aa0aeaa584b5a54d43f2f21d6c08> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x92000 - 0x97fff com.apple.backup.framework 1.0 (1.0) /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0xa1000 - 0xaefe7 com.apple.opengl 1.5.9 (1.5.9) <7e5048a2677b41098c84045305f42f7f> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x131000 - 0x1e8ff3 com.apple.QTKit 7.6 (1290) /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x262000 - 0x26cffe com.apple.URLMount 3.1.1 (3.1.1) <a6aece1c9c34992e08acf4b68e523f90> /System/Library/PrivateFrameworks/URLMount.framework/Versions/A/URLMount
0x274000 - 0x274ffc com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x3d9000 - 0x654fe7 com.apple.Foundation 6.5.7 (677.22) <8fe77b5d15ecdae1240b4cb604fc6d0b> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7b2000 - 0x7cfff7 com.apple.QuickLookFramework 1.3.1 (170.9) /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7e3000 - 0x7eafe9 libgcc_s.1.dylib ??? (???) <e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
0x7f0000 - 0x7f4fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x7f8000 - 0x7f8ffd com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0xd3f000 - 0x153dfef com.apple.AppKit 6.5.6 (949.43) <a3a300499bbe4f1dfebf71d752d01916> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x1a7e000 - 0x1ab5fff com.apple.SystemConfiguration 1.9.2 (1.9.2) <eab546255ac099b9616df999c9359d0e> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x1ad4000 - 0x1df9fe2 com.apple.QuickTime 7.6.0 (1290) <bc0920abbbaad03f5513ac7ffbd30633> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x1ebf000 - 0x203efff com.apple.AddressBook.framework 4.1.1 (699) <60ddae72a1df8ddbc5c53df92f372b76> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x211a000 - 0x2169fff com.apple.QuickLookUIFramework 1.3.1 (170.9) /System/Library/PrivateFrameworks/QuickLookUI.framework/Versions/A/QuickLookUI
0x21a0000 - 0x2307ff3 libSystem.B.dylib ??? (???) <d68880dfb1f8becdbdac6928db1510fb> /usr/lib/libSystem.B.dylib
0x2396000 - 0x2476fff libobjc.A.dylib ??? (???) <400e943f9e8a678eea22a1d1205490ee> /usr/lib/libobjc.A.dylib
0x24e8000 - 0x261bfff com.apple.CoreFoundation 6.5.5 (476.17) <4a70c8dbb582118e31412c53dc1f407f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x2713000 - 0x2865ff3 com.apple.audio.toolbox.AudioToolbox 1.5.2 (1.5.2) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x28da000 - 0x29bfff3 com.apple.CoreData 100.1 (186) <50219bcb005cb15ea999a19391a8d523> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x2a3a000 - 0x2ac4fef com.apple.DesktopServices 1.4.7 (1.4.7) <c64f04641052fdaa0f0cdee3564a0fd3> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x2b0f000 - 0x2e17fff com.apple.HIToolbox 1.5.4 (???) <3747086ba21ee419708a5cab946c8ba6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x2f75000 - 0x3000fff com.apple.framework.IOKit 1.5.1 (???) <f9f5f0d070e197a832d86751e1d44545> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x3026000 - 0x33c3fef com.apple.QuartzCore 1.5.7 (1.5.7) <2fed2dd7565c84a0f0c608d41d4d172c> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x34bd000 - 0x368bff3 com.apple.security 5.0.4 (34102) <55dda7486df4e8e1d61505be16f83a1c> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x37d0000 - 0x37d9fff com.apple.speech.recognition.framework 3.7.24 (3.7.24) <da2d8411921a3fd8bc898dc753b7f3ee> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x37e3000 - 0x380efe7 libauto.dylib ??? (???) <2e44c523b851e8e25f05d13a48070a58> /usr/lib/libauto.dylib
0x381c000 - 0x3954ff7 libicucore.A.dylib ??? (???) <18098dcf431603fe47ee027a60006c85> /usr/lib/libicucore.A.dylib
0x39a8000 - 0x3a89ff7 libxml2.2.dylib ??? (???) <306036e0070330e35045650e6d9f0d05> /usr/lib/libxml2.2.dylib
0x3ab6000 - 0x3ac4ffd libz.1.dylib ??? (???) <a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
0x3aca000 - 0x3b04fe7 com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x3b24000 - 0x3ba1feb com.apple.audio.CoreAudio 3.1.1 (3.1.1) <f35477a5e23db0fa43233c37da01ae1c> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x3bf6000 - 0x3c89ff3 com.apple.ApplicationServices.ATS 3.4 (???) <8c51de0ec3deaef416578cd59df38754> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x3cb0000 - 0x3d7bfff com.apple.ColorSync 4.5.1 (4.5.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x3dbc000 - 0x445cfff com.apple.CoreGraphics 1.407.2 (???) <3a91d1037afde01d1d8acdf9cd1caa14> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x452c000 - 0x4586ff7 com.apple.CoreText 2.0.4 (???) <f9a90116ae34a2b0d84e87734766fb3a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x45c6000 - 0x4617ff7 com.apple.HIServices 1.7.0 (???) <01b690d1f376e400ac873105533e39eb> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x4641000 - 0x4787ff7 com.apple.ImageIO.framework 2.0.4 (2.0.4) <b407f06ff9b6893899e2e399cb65c953> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x47df000 - 0x47efffc com.apple.LangAnalysis 1.6.4 (1.6.4) <bc7eb703ddc37bf85adf93e35efd3947> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x47fc000 - 0x48a3feb com.apple.QD 3.11.54 (???) <c31150b40fcc27c195de40f0ae138666> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x48cc000 - 0x48dcfff com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <273d96ff861dc68be659c07ef56f599a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x48eb000 - 0x4bc5ff3 com.apple.CoreServices.CarbonCore 786.11 (786.11) <f06fe5d92d56ac5aa52d1ba182745924> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x4c2f000 - 0x4cccfe4 com.apple.CFNetwork 422.15.2 (422.15.2) <80851410a5592b7c3b149b2ff849bcc1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x4d44000 - 0x4d8dfef com.apple.Metadata 10.5.2 (398.25) <e0572f20350523116f23000676122a8d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x4da9000 - 0x4e63fe3 com.apple.CoreServices.OSServices 226.5 (226.5) <ef9945b1304495f3e8085c935f1b81e3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x4ec8000 - 0x4f47ff5 com.apple.SearchKit 1.2.1 (1.2.1) <f28f8dd0f155a6453411a0c9b5702764> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x4f8a000 - 0x4fb9fe3 com.apple.AE 402.3 (402.3) <4cb9ef65cf116d6dd424f0ce98c2d015> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x4fd1000 - 0x505dff7 com.apple.LaunchServices 290.3 (290.3) <6f9629f4ed1ba3bb313548e6838b2888> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x50a3000 - 0x50b9fff com.apple.DictionaryServices 1.0.0 (1.0.0) <7d20b8d1fb238c3e71d0fa6fda18c4f7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x50cb000 - 0x50d2ffe libbsm.dylib ??? (???) <fa7ae5f1a621d9b69e7e18747c9405fb> /usr/lib/libbsm.dylib
0x50d9000 - 0x5136ffb libstdc++.6.dylib ??? (???) <f75e5133d72769de5ce6c06153fc65f6> /usr/lib/libstdc++.6.dylib
0x5187000 - 0x520eff7 libsqlite3.0.dylib ??? (???) <eeedc8bf6881ac9f2c1954b1c8037720> /usr/lib/libsqlite3.0.dylib
0x521b000 - 0x523ffff libxslt.1.dylib ??? (???) <0a9778d6368ae668826f446878deb99b> /usr/lib/libxslt.1.dylib
0x5249000 - 0x52fbffb libcrypto.0.9.7.dylib ??? (???) <75b80bff0d5cfaf10b6b6fe982da3578> /usr/lib/libcrypto.0.9.7.dylib
0x534a000 - 0x5411ff2 com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x5421000 - 0x5421ffd com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x5425000 - 0x54a2fef libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x54b0000 - 0x54ddfeb libvDSP.dylib ??? (???) <4daafed78a471133ec30b3ae634b6d3e> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x54e9000 - 0x58f9fef libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x593f000 - 0x5cfdfea libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x5d33000 - 0x5d52ffa libJPEG.dylib ??? (???) <b822342bcc764c83d4557a8b67fa0c1c> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x5d5a000 - 0x5d99fef libTIFF.dylib ??? (???) <d4bcc9b9c508e53849d2d46bb6900922> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x5da4000 - 0x5da8fff libGIF.dylib ??? (???) <7714ae24eb64b48fa719fb99bcbe34f3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x5dae000 - 0x5dc9ffb libPng.dylib ??? (???) <0d6b991afc831ea06f2958e5933d33dd> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x5dd1000 - 0x5dd3ff5 libRadiance.dylib ??? (???) <82d606c49f5dc77231f9d0e2be9ed6ab> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x5dd8000 - 0x5e00fff libcups.2.dylib ??? (???) <16bec7c6a004f744804e2281a1b1c094> /usr/lib/libcups.2.dylib
0x5e0b000 - 0x5e29fff libresolv.9.dylib ??? (???) <9ed809256ce8913cddc3269c2e364654> /usr/lib/libresolv.9.dylib
0x5e33000 - 0x5e33ffd com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x5e37000 - 0x5e37ffb com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x5e3b000 - 0x5e45feb com.apple.audio.SoundManager 3.9.2 (3.9.2) <df077a8048afc3075c6f2d9e7780e78e> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x5e4e000 - 0x5e8cff7 libGLImage.dylib ??? (???) <1123b8a48bcbe9cc7aa8dd8e1a214a66> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x5e96000 - 0x5e97ffc libffi.dylib ??? (???) <eaf10b99a3fbc4920b175809407466c0> /usr/lib/libffi.dylib
0x5e9c000 - 0x5eb4ff7 com.apple.CoreVideo 1.6.0 (20.0) <c0d869876af51283a160cd2224a23abf> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x5ec8000 - 0x5f21ff7 libGLU.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x5f35000 - 0x5f41ffe libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x5f4f000 - 0x6420f3e libGLProgrammability.dylib ??? (???) <5d283543ac844e7c6fa3440ac56cd265> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x654d000 - 0x6552fff com.apple.CommonPanels 1.2.4 (85) <c135f02edd6b2e2864311e0b9d08a98d> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x655b000 - 0x655efff com.apple.help 1.1 (36) <1a25a8fbb49a830efb31d5c0a52939cd> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x6564000 - 0x65c0ff7 com.apple.htmlrendering 68 (1.1.3) <1c5c0c417891b920dfe139385fc6c155> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x65ee000 - 0x6603ffb com.apple.ImageCapture 5.0.1 (5.0.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x661e000 - 0x66b1fff com.apple.ink.framework 101.3 (86) <d4c85b5cafa8027fff042b84a8be71dc> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x66d0000 - 0x6712fef com.apple.NavigationServices 3.5.2 (163) <72cdc9d21f6690837870923e7b8ca358> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x6740000 - 0x6758fff com.apple.openscripting 1.2.8 (???) <0129d2f750f5ddcb92f4acf8a3541952> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x676a000 - 0x676cfff com.apple.securityhi 3.0 (30817) <40562b85d99118354c974e76c32fa6fb> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x6772000 - 0x679bfff com.apple.CoreMediaPrivate 15.0 (15.0) /System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CoreMediaPrivate
0x67ae000 - 0x67edfff com.apple.CoreMediaIOServicesPrivate 15.0 (15.0) /System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/CoreMediaIOServicesPrivate
0x6815000 - 0x6815ff8 com.apple.Cocoa 6.5 (???) <a1bc9247cf65c20f1a44d0973cbe649c> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x6819000 - 0x69d5ff3 com.apple.QuartzComposer 2.1 (106.13) <40f034e8c8fd31c9081f5283dcf22b78> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
0x6aec000 - 0x6b5efff com.apple.PDFKit 2.1.2 (2.1.2) /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit
0x6ba5000 - 0x6bd6ffb com.apple.quartzfilters 1.5.0 (1.5.0) <92b4f39479fdcabae0d8f53febd22fad> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters
0x6bfe000 - 0x6d36fe7 com.apple.imageKit 1.0.2 (1.0) <2e354566521df8b1e3a78e9aeab5e6b4> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
0x6e03000 - 0x6f68fe7 com.apple.JavaScriptCore 5528 (5528.15) <a1edf2b00622f9d833987cb333b432ac> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x6fbc000 - 0x6fcbffe com.apple.DSObjCWrappers.Framework 1.3 (1.3) <182986b74247b459b2a67a47071bdc6b> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers
0x6fd9000 - 0x6fdefff com.apple.DisplayServicesFW 2.0.2 (2.0.2) <97878a73074e7da4fe31ea010a5d5ae1> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices
0x6fe7000 - 0x7005ff3 com.apple.DirectoryService.Framework 3.5.5 (3.5.5) <f8931f64103c8a86b82e9714352f4323> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x7012000 - 0x7012ffe com.apple.MonitorPanelFramework 1.2.0 (1.2.0) <1f4c10fcc17187a6f106e0a0be8236b0> /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPanel
0x7018000 - 0x704afff com.apple.LDAPFramework 1.4.5 (110) <e9e44dec1fd4b049276257c7cc97b423> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7055000 - 0x7064fff libsasl2.2.dylib ??? (???) <bb7971ca2f609c070f87786a93d1041e> /usr/lib/libsasl2.2.dylib
0x706c000 - 0x7090feb libssl.0.9.7.dylib ??? (???) <d04156c610530ca44979c899834fc24d> /usr/lib/libssl.0.9.7.dylib
0x70b9000 - 0x70c5ffb +com.fsb.SafariBlock ??? (2.2r1) <fe7dd96f3e475128f5b951956f41f1c9> /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock
0x7300000 - 0x730bfe7 libCSync.A.dylib ??? (???) <e6aceed359bd228f42bc1246af5919c9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x7314000 - 0x733cff7 com.apple.shortcut 1 (1.0) <35cd17d0179ca839c5fb08694f3dc5ef> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x735b000 - 0x7367ff9 com.apple.helpdata 1.0.1 (14.2) /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7376000 - 0x73b7fe7 libRIP.A.dylib ??? (???) <5d0b5af7992e14de017f9a9c7cb05960> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x73f0000 - 0x73f5ff3 libCGXCoreImage.A.dylib ??? (???) <375e0cdb64b043378dbf637992bbfeb0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
0x7589000 - 0x758efff com.apple.DictionaryServiceComponent 1.1 (1.1) <0c718fcdccb0e50ce699cb46073b5b88> /System/Library/Components/DictionaryService.component/Contents/MacOS/DictionaryService
0x76e2000 - 0x76e9ff7 libCGATS.A.dylib ??? (???) <386dce4b28448fb86e33e06ac466f4d8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x189c5000 - 0x18bbdfff com.apple.RawCamera.bundle 2.0.13 (435) <083354ccec68bf7c9fc99523a5838f92> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x1cf5d000 - 0x1d14ffea +com.elgato.mpegsupport EyeTV MPEG Support 1.0.7 (build 43) (1.0.7) /Library/QuickTime/EyeTV MPEG Support.component/Contents/MacOS/EyeTV MPEG Support
0x20000000 - 0x200b0fff edu.mit.Kerberos 6.0.12 (6.0.12) <685cc018c133668d0d3ac6a1cb63cff9> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x64b00000 - 0x64b06fff com.apple.print.framework.Print 218.0.2 (220.1) <6c2ddea45d9cdff9a9be0666a13e2dd4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
0xfa100000 - 0xfa17aff8 com.apple.print.framework.PrintCore 5.5.3 (245.3) <98633ef67d419c1b02f56556cb4d843d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib



That's weird, exc_bad_access is akin to null pointer error, its when you are releasing an object that wasnt instantiated by you...

[MBHockey]

I checked the others, most are of that type but some are EXC_BAD_INSTRUCTION (SIGILL)

I'm don't know what all that other stuff you said means =)

[harshw]

I checked the others, most are of that type but some are EXC_BAD_INSTRUCTION (SIGILL)

I'm don't know what all that other stuff you said means =)

It's a memory access error, happens when a program tries to free memory that doesn't belong to it. Usually bad coding would cause it, or to stretch it ... bad memory. But a whacky SSD ? Hmmm ... weird

What are your system specs again ? RAM is Apple branded ?

[MBHockey]

It's a memory access error, happens when a program tries to free memory that doesn't belong to it. Usually bad coding would cause it, or to stretch it ... bad memory. But a whacky SSD ? Hmmm ... weird

What are your system specs again ? RAM is Apple branded ?

No, the ram is Crucial.

Sounds like it's time for memtest =)

I've used Crucial ram in Macs since 2002 and never had a problem though.

[harshw]

No, the ram is Crucial.

Sounds like it's time for memtest =)

I've used Crucial ram in Macs since 2002 and never had a problem though.

Memtest wont reveal anything. If your RAM is non Apple AND you are using a new Unibody Macbook or Macbook Pro: try removing the non Apple RAM or switching to Apple RAM. If it works without crashing then it is the non Apple RAM. Remember this is only for Unibody laptops and the new Macs with DDR3 ( not Mac Pros )

Seems that Apple RAM has some esoteric SPD info in the EEPROM that the Mac reads and or something like that and consequently non-Apple RAM doesn't have this and hence causes problems

Safest is to go with Apple RAM on the Unibody.

[mikest]

We have a FW update coming that does address some mac sleep and hibernation issues.

I would consider flashing this when i get the go ahead to release.

I will give it a try, is this days or weeks out?

[MBHockey]

Interesting. I will pop out this ram and throw in the stock 2GB ram and see if i get any Spotlight crashes over the next few days.

If i have to return this ram to crucial, can you explain to them why it sucks (because I won't be able to) ;)

I'll report back about the ram.

[harshw]

I didn't think these were bleeding edge. I am not a fan of bleeding edge. My computers are tools. They are what I use to make a living. I can't afford bleeding edge. My customers will leave me and my income will vanish if I use bleeding edge. SSDs have been around for a few years now, and are on their way to going mainstream. OCZ has years of SSD development/sales. I simply thought I'd go 3rd party (OCZ) rather than pay the "apple tax" for a smaller, more expensive, slower Apple SSD. I wasn't hot-rodding my Mac, it's pure stock, except for the hard drive that they make very easy for the user to replace.

I don't mind slow. My last laptop is 1.3Ghz G4 with a 5400 RPM drive. Plenty fast. But more importantly, incredibly reliable. I only rebooted a few times a year, with uptimes usually between 90 and 180 days at reboot time.

Hi Jerry

Yeah it can be bad if you depend on this Mac for a liveliehood and it's causing problems ... unfortunately modern MLC SSDs are bleeding edge currently. Take the TRIM/DISCARD stuff - everyone is talking about it but it's not standardised 100%. And if the TRIM makes it to the firmware, OS X, XP and Vista won't support it out of the door. And all the filesystems still are optimised for HDDs and not SSDs. Even the drivers and specs are HDD specific - there is no "Head Unload/Park" on a SSD for example but the ATA driver makes deep assumptions about this.

If it is business critical, the best bet would be to go with Apple SSDs as one could then get support - although Apple isn't exactly known for same day/next day business critical support unless you have applecare premium. IIRC that is only for server stuff

I once had a problem with enterprise drives & RAID from one of the biggest vendors and I was working for a giant multinational - the largest company in its area. I had all the enterprise level support plans etc. After one week of downtime, arguing, hassle with tech support on a 6TB critical database, I found the answer to my problems in a user forum :) The tech support sent an email another week later saying they couldnt solve my problem. My colleague was angry that the company had paid $$$ for enterprise drives, enterprise RAID, enterprise OS, enterprise support plans, enterprise XXX and it was all B.S.

Does it mean I would recommend non-enterprise stuff and SLAs for business critical stuff ? Probably not :-( YMMV though ...

Anyways - back to the issue at hand. The latest firmware due Real Soon Now is supposed to have fixes for Macs specifically. I'm really hoping they solve these mysterious freezes ...

[harshw]

Interesting. I will pop out this ram and throw in the stock 2GB ram and see if i get any Spotlight crashes over the next few days.

If i have to return this ram to crucial, can you explain to them why it sucks (because I won't be able to) ;)

I'll report back about the ram.

Crucial and OWC are aware of the countless posts in Apple discussion forums and will take it back without comment or query or will at least keep sending you kits to try till you get one without issue.

Make sure you have 10.5.6 AND the EFI updates. Sometimes that doesn't help and you need to change the RAM kit until you find one that works - or then go with Apple RAM. After a bad experience I had to order a MacBook with 4GB of Apple $$$ RAM as BTO :|

http://forums.macrumors.com/showthread.php?t=643489
http://discussions.apple.com/thread.jspa?messageID=8805943?
http://discussions.apple.com/thread.jspa?messageID=9004405?

So it could be the RAM. If it works fine with the standard 2GB ... you'll know the Crucial kit was the culprit.

[harshw]

I didn't think these were bleeding edge. I am not a fan of bleeding edge. My computers are tools. They are what I use to make a living. I can't afford bleeding edge. My customers will leave me and my income will vanish if I use bleeding edge. SSDs have been around for a few years now, and are on their way to going mainstream. OCZ has years of SSD development/sales. I simply thought I'd go 3rd party (OCZ) rather than pay the "apple tax" for a smaller, more expensive, slower Apple SSD. I wasn't hot-rodding my Mac, it's pure stock, except for the hard drive that they make very easy for the user to replace.

I don't mind slow. My last laptop is 1.3Ghz G4 with a 5400 RPM drive. Plenty fast. But more importantly, incredibly reliable. I only rebooted a few times a year, with uptimes usually between 90 and 180 days at reboot time.

http://www.ocztechnology.com/products/flash_drives/ocz_vertex_series_mac_edition_sata_ii_2_5-ssd

Now they have to support the Macs ... there's a list on the product page with validated models.

[MikhailT]

Tony just released the 1.10 firmware that might contain sleep/hibernation fixes for macs but might not since it says Mac Pros. (Mod just said it is for all Macs, not just Mac Pros)

http://www.ocztechnologyforum.com/forum/showthread.php?t=54648

Let's test this firmware out and see that'll fix our issues.

[FieryFurnace]

http://www.ocztechnology.com/products/flash_drives/ocz_vertex_series_mac_edition_sata_ii_2_5-ssd

Now they have to support the Macs ... there's a list on the product page with validated models.

What is the difference between that new Vertex Mac Edition and the "normal" Vertex that I use now???

And there won't be any Mac support for the normal Vertex anymore?

[HDCHOPPER]

same drive different FW

[FieryFurnace]

same drive different FW

Is the FW available for those Mac users with the normal Vertex, and will it be later too?

Why does OCZ releases two different Vertex if they are the same, only with different FW on the SSD?

[HDCHOPPER]

http://www.ocztechnologyforum.com/forum/showthread.php?t=54648

[jerry]

How long has this new "Mac Specific" firmware been in the works?

[MikhailT]

How long has this new "Mac Specific" firmware been in the works?

since last firmware? it isn't really mac specific firmware, it just contain some fixes for mac users, specifically the sleep/hibernation. beside that and a few other issues, vertex works pretty well out of the box for Macs. It doesn't really need special line of Vertex, it is just that OCZ wanted Apple's certification and this Mac edition is then made.

[MBHockey]

Flashed to v1.10 last night, and my MacBook woke up without issue this morning (although time will tell...)

I also did a clean install of OS X and have yet to bring all my data over. I replaced my crucial ram with the original 2 GB stock ram to see if that fixes other issues).

I still unselected 'spin down hard drive' in Energy Saver for both battery and power adapter, and shut off the sudden motion sensor. I will leave the sleep mode on the default it comes with (3).

[MikhailT]

Flashed to v1.10 last night, and my MacBook woke up without issue this morning (although time will tell...)

I also did a clean install of OS X and have yet to bring all my data over. I replaced my crucial ram with the original 2 GB stock ram to see if that fixes other issues).

I still unselected 'spin down hard drive' in Energy Saver for both battery and power adapter, and shut off the sudden motion sensor. I will leave the sleep mode on the default it comes with (3).

It doesn't really help us nor OCZ if you do those tweaks. if you leave it with defaults setting and it does cause issue, then we would know the firmware still isn't Mac friendly.

I know it sound like we are really the beta testers for OCZ but think of how many Mac users we help by doing this.

[MBHockey]

I always select "don't spin down hard disk". The sleep mode seemed to have no effect on the crashes, and it makes sense to save space with mode "0".

I will reenable the SMS, though, since people had experienced kernel panics with the vertex and this feature enabled.

[MikhailT]

I always select "don't spin down hard disk". The sleep mode seemed to have no effect on the crashes, and it makes sense to save space with mode "0".

I will reenable the SMS, though, since people had experienced kernel panics with the vertex and this feature enabled.

I experienced kernel panic turning off SMS. Which is funny..not.

[MBHockey]

I re-enabled the SMS and proceeded to shake the macbook like a polaroid picture....

no panic :D

[harshw]

I re-enabled the SMS and proceeded to shake the macbook like a polaroid picture....

no panic :D

It would be funny if your "drive" crashed because of the shaking ;)

[MBHockey]

;)

So far so good on my MacBook (was gone from 7 am to 8 pm though; macbook was sleeping on the desk).

Hopefully this keeps up!

[harshw]

Yeah, mine's working fine too. But keep in mind that I have had one crash per week so it could be a week before I notice a lockup or a freeze. But let's hope this firmware solved all those lockup/hang/beachball/freeze issues.

[MBHockey]

Yeah, let's give it a week :)

I've noticed my machine boots up about 4-5 seconds faster on v1.10 firmware. Maybe this is due to the clean install of the OS though?

[harshw]

Yeah, let's give it a week :)

I've noticed my machine boots up about 4-5 seconds faster on v1.10 firmware. Maybe this is due to the clean install of the OS though?

Yeah. OSX like Windows and Linux, slows down as you add stuff. Mounting with noatime helps too.

If you boot from USB / CD then sometimes the boot process can slow down as OSX 'remembers' the last boot disk location. Doing a PRAM reset helps since it restores the boot order to default.

[MBHockey]

This is after I've replaced all 100 gb of data...I think cloning may have been the culprit.

[harshw]

This is after I've replaced all 100 gb of data...I think cloning may have been the culprit.

Did you clone with CCC ?

[MBHockey]

Yeah I used CCC. It makes no sense, I know. :)

[MBHockey]

Has anyone experienced lockups on v1.10 as of yet? Has it been smooth sailing for everyone else like it has for me so far?

[harshw]

Has anyone experienced lockups on v1.10 as of yet? Has it been smooth sailing for everyone else like it has for me so far?

No lockups yet. Booted into Linux, booted back. Slept and resumed. All okay so far - cross fingers and knock on wood.

[MBHockey]

Disappointed to report I just had the same type of lockup on v1.10 that I was getting on 1275, so the problem has not been fixed yet (stock MacBook aside from the SSD).

Woke up the computer this morning and it was fine for about 10 minutes, and then it just froze up. Beach balling on everything I touched, had to do a hard rest and there's nothing in the logs.

:beat:

[harshw]

Disappointed to report I just had the same type of lockup on v1.10 that I was getting on 1275, so the problem has not been fixed yet (stock MacBook aside from the SSD).

Woke up the computer this morning and it was fine for about 10 minutes, and then it just froze up. Beach balling on everything I touched, had to do a hard rest and there's nothing in the logs.

:beat:

OUCH

Okays so now the only option is the setup a remote syslog server and edit syslogd.conf to send all messages to that server. In this way, we can check the messages even if the machine hangs. Now all I need is a cheap Atom or ION box running Ubuntu and connected to the network ...

[HDCHOPPER]

harshw I have a few used machines here you could have one of them for that , all you have to do is come pick it up ;)

[MBHockey]

I really just don't have the time to deal with this. I may just exchange it for an intel if newegg lets me.

It's a shame because it's such a promising drive. But I really do feel like a beta tester at this point =\

[harshw]

harshw I have a few used machines here you could have one of them for that , all you have to do is come pick it up ;)

:D Yep, it's just a little round trip but I think Phoenix has much better weather than London right now so it would be worth it ...

I have a HTPC that runs Vista and consumes 30W idle. I'm going to see how to setup a syslog server there (maybe via Services For Unix ...) My MacBook is in daily use 24/7 and the if something happens and we get a few entries into the logs - that would be a start.

@MBHockey: I know it sucks. But if the Mac variants are 'Apple' certified and they have the same freezes/lockups - then OCZ/Indilinx pretty much will solve the problem, they don't have a choice. I went with OCZ over Intel solely because of the upgradable firmware. I got burned by the Bootcamp thingy being an early adopter, so all I can say is that if one is using bleeding edge tech ... well then you accept that one bleeds :cry:

[MBHockey]

@MBHockey: I know it sucks. But if the Mac variants are 'Apple' certified and they have the same freezes/lockups - then OCZ/Indilinx pretty much will solve the problem, they don't have a choice. I went with OCZ over Intel solely because of the upgradable firmware. I got burned by the Bootcamp thingy being an early adopter, so all I can say is that if one is using bleeding edge tech ... well then you accept that one bleeds :cry:

For $730 I expect it to work without the minute to minute fear that the machine could go down at any instant. That's not "bleeding edge"; that's broken.

[AppleUser]

For $730 I expect it to work without the minute to minute fear that the machine could go down at any instant. That's not "bleeding edge"; that's broken.

Very true. Although I'm not going descend into lawyerisms.

I'm still using 1257 as, although I had a waking beach ball this morning, it works 90% of the time and I've not had a corruption yet (this is the real key for me). I decided after that I'd wait and see what develops - perhaps even lag behind a release.

Had I been working with the laptop on battery and this happen I would be annoyed however I save/quit all applications before manually putting the thing to sleep. I've been running on main power most of the time at the moment in the office and at home.

On the positive side I think it's superb that OCZ have chosen to address the Apple market in such a constructive manner. It's a market segment with a fixed hardware profile making the support easier, although the users may be more demanding in terms of expecting Boom - it just works.

[harshw]

I'm still using 1257 as, although I had a waking beach ball this morning, it works 90% of the time and I've not had a corruption yet

And this is the real surprising part. Ok I know that HFS+ is journaled, but still it is very surprising that after four beachballs in five weeks, hard resets - I've had NO corruption on the filesystem. So somehow the drive disappears or shuts down somehow after completing commands/flushing cache.

I think this is important info for engineers ...

[jgo]

How long were you guys running the macs before you noticed beach balls and lock-ups?

I have been using fw 1199 on my 17" UMBP for the past few days and have not had a single problem with sleep, beach balls, or lock ups.

It makes you begin to believe that there is no reason to upgrade the firmware...however, during this time I have been frantically trying to flash the drive using my computer and my wife's older MBP - no success. My next resort is to try using one of the Dell's at my work - just have to do it when the IT guys are not around.

[Tony]

you guys with issues i have a simple question for ya.

Throughout the whole time you have had issues are you working off an imaged drive or a drive that was fresh installed?

Indilinx never image as far as I am aware, all tests are always from fresh installs.

So that brings me to those without issues.

Did you fresh install to the drive?

Now we know the drive can sleep and hibernate just fine(vista XP)...the issue has to be driver, OS or interaction between OS/driver and FW on the drive...

I am starting to feel Apple need to take a look at this also, just quoting its upto OCZ to fix the issue does not always work, if they have an EFI issue or OSX issue then OCZ can not touch either as they are covered under Apples copyright, this is why its actually illegal to modify bios files for boards..hence I stopped doing it ;)

harshw...what would be the most useful thing I could ask inilinx to do that would help you guys debug this?

[MBHockey]

you guys with issues i have a simple question for ya.

Throughout the whole time you have had issues are you working off an imaged drive or a drive that was fresh installed?

Indilinx never image as far as I am aware, all tests are always from fresh installs.

So that brings me to those without issues.

Did you fresh install to the drive?

Now we know the drive can sleep and hibernate just fine(vista XP)...the issue has to be driver, OS or interaction between OS/driver and FW on the drive...

I am starting to feel Apple need to take a look at this also, just quoting its upto OCZ to fix the issue does not always work, if they have an EFI issue or OSX issue then OCZ can not touch either as they are covered under Apples copyright, this is why its actually illegal to modify bios files for boards..hence I stopped doing it ;)

harshw...what would be the most useful thing I could ask inilinx to do that would help you guys debug this?

1199 - Fresh install - lockups
1275 - Clone - lockups
1.10 - fresh install - lockups

I would really hope that if it was something as simple as that they could have figured it out by now.

[MikhailT]

you guys with issues i have a simple question for ya.

Throughout the whole time you have had issues are you working off an imaged drive or a drive that was fresh installed?

Indilinx never image as far as I am aware, all tests are always from fresh installs.

So that brings me to those without issues.

Did you fresh install to the drive?

Now we know the drive can sleep and hibernate just fine(vista XP)...the issue has to be driver, OS or interaction between OS/driver and FW on the drive...

I am starting to feel Apple need to take a look at this also, just quoting its upto OCZ to fix the issue does not always work, if they have an EFI issue or OSX issue then OCZ can not touch either as they are covered under Apples copyright, this is why its actually illegal to modify bios files for boards..hence I stopped doing it ;)

harshw...what would be the most useful thing I could ask inilinx to do that would help you guys debug this?

At most, a logging system. Some way to put the SSD into debug verbose mode so that we can get more information on why it crashed.

Tony, would you be willing to talk to Apple on our behalf if we write up all the information ourselves and send it to you? It would more organized if we do it this way.

[harshw]

Throughout the whole time you have had issues are you working off an imaged drive or a drive that was fresh installed?

It has happened on both copied and fresh installed drives. I never clone drives via block level copying, I create a new partition on the disk and then use CCC to do a file level copy. This copies backed up files to an already existing partition and then sets permissions, "blesses" the partition to make it bootable, etc. Pretty much the same as an install ...

The bug is not dependant on heavy disk or network activity. Seems to me more like a timing issue in code somewhere, either in firmware or in Apple drivers. Mostly the code works 99% but the 1% it doesnt work it causes the drive to hang.



harshw...what would be the most useful thing I could ask inilinx to do that would help you guys debug this?

If OCZ/Indilinx has a relationship with Apple then they can use it to get debug variants for AHCI/ATA kexts (basically the AHCI and SATA drivers), we could run these and set output to a remote syslog server.

Or if Indilinx can build a debug version of firmware for the drives that can record the last 65,536 commands sent to the drive or something similar - this should also help in crash analysis since the drives will give a more accurate picture of what went on. A few of us have Macs and Windows so the tools to recover debug info from the drives could be Win32 as well.

Since the problem is so random, I don't think debugging it is going to be easy either ...

[harshw]

Tony

I had a freeze around 8 minutes ago. This time, I put the Macbook to sleep by closing the lid, took the drive out, unplugged and plugged it back in - system started working again ! I guess this points to either the drive having problems with power states or then the plugging / unplugging caused the drive to reset hence everything worked.

Can anyone who experiences this problem and owns a Unibody try this out ? Please close the laptop lid BEFORE opening the bottom compartment though.

I'll attached the system logs in a PM

[MBHockey]

I don't understand why end-users are being asked for this info. It makes me feel like OCZ/Indilinx don't care enough to try and fix it themselves (regardless of what is posted in the changelogs).

Presumably, OCZ/Indilinx have Macs to test their drives (especially now) so why can't they just work on this problem themselves? It's not like it's endemic to a few people with odd Mac setups -- these are stock machines -- and it is a problem that is happening on all Mac users who regularly sleep/wake their machines. They just have to set up some way to debug the drive and then use it for two days while sleeping and waking it regularly. I mean, how did they go about testing this problem in order to come up with a "fix" for the 1.10 firmware? They must have had some method of debugging it.


I don't mind helping out, but it kind of makes me feel like they are saying, "we're too busy to look into this Mac-specific problem -- try to figure it out yourselves"

[MikhailT]

Tony

I had a freeze around 8 minutes ago. This time, I put the Macbook to sleep by closing the lid, took the drive out, unplugged and plugged it back in - system started working again ! I guess this points to either the drive having problems with power states or then the plugging / unplugging caused the drive to reset hence everything worked.

Can anyone who experiences this problem and owns a Unibody try this out ? Please close the laptop lid BEFORE opening the bottom compartment though.

I'll attached the system logs in a PM

Can you also PM me the system logs? Or attach it to this post? Many people would love to see it.

[MBHockey]

Tony

I had a freeze around 8 minutes ago. This time, I put the Macbook to sleep by closing the lid, took the drive out, unplugged and plugged it back in - system started working again ! I guess this points to either the drive having problems with power states or then the plugging / unplugging caused the drive to reset hence everything worked.

Can anyone who experiences this problem and owns a Unibody try this out ? Please close the laptop lid BEFORE opening the bottom compartment though.

I'll attached the system logs in a PM


Harsh, i guess we are getting somewhere.

Let me get this straight though so I know how to go about it when it happens.

Wake up Mac --> It starts to hang (beach balls galore) --> put lid back down to initiate sleep --> remove drive from SATA cable, and then replug it in --> wake computer

So the SSD is removed and then hot-plugged while the system is sleeping?

[MikhailT]

I don't understand why end-users are being asked for this info. It makes me feel like OCZ/Indilinx don't care enough to try and fix it themselves (regardless of what is posted in the changelogs).

Presumably, OCZ/Indilinx have Macs to test their drives (especially now) so why can't they just work on this problem themselves? It's not like it's endemic to a few people with odd Mac setups -- these are stock machines -- and it is a problem that is happening on all Mac users who regularly sleep/wake their machines. They just have to set up some way to debug the drive and then use it for two days while sleeping and waking it regularly. I mean, how did they go about testing this problem in order to come up with a "fix" for the 1.10 firmware? They must have had some method of debugging it.

It just seems so much more effort is required with a line of middle-men to go through (which means it is going to take a lot longer to fix) in order to collect and relay this information back to OCZ/Indilinx that it begs the question, "Isn't it easier for them to do it themselves?"

I don't mind helping out, but it kind of makes me feel like they are saying, "we're too busy to look into this Mac-specific problem -- try to figure it out yourselves"

It's too random to force the issue to come out. I have slept the laptop 20 times in a day just to see if I could get a freeze, nothing. Two weeks later, blam, I got the freeze. Tony did said that Indilinx ran it 10 times and they got it 1 out of 10 times. They did look into it, they thought they fixed it in 1.10. Now it is looking like 1.10 isn't the real fix for us.

[MBHockey]

Yeah, i didn't mean to come off too harsh in my last post. I like supporting small, innovative companies like OCZ. I just hope they are doing the right thing on their end. The real message is it kind of feels like we're out in the cold here because we don't have PCs running XP and Vista.

[harshw]

The real message is it kind of feels like we're out in the cold here because we don't have PCs running XP and Vista.

No ... the dudes running XP and Vista have problems too, just that they are different problems :chit:

[MikhailT]

Harsh, i guess we are getting somewhere.

Let me get this straight though so I know how to go about it when it happens.

Wake up Mac --> It starts to hang (beach balls galore) --> put lid back down to initiate sleep --> remove drive from SATA cable, and then replug it in --> wake computer

So the SSD is removed and then hot-plugged while the system is sleeping?

This is starting to feel like a major issue that I have with eSATA drives connected to MBP, it was a sleep issue. The system was inactive for certain amount of time, the eSATA drive went to sleep, blam there was a freeze in any operations that requires the eSATA drive, like scratch on eSATA or file transfers to eSATA. The only way to actually get it back was to unplug and replug in the eSATA cable.


Did anybody get a freeze while they were working and doing something, or was it during some kind of inactivity no matter how short?

[HDCHOPPER]

It's ok MB I thought that was one of the best controlled & thought out rants to date ....

[MBHockey]

It's ok MB I thought that was one of the best controlled & thought out rants to date ....

haha ;)

@harshw:

Did i have that sequence right for getting the drive to work again after a hang?

[Tony]

The reason I ask you guys to do this is OCZ went to Apple and tested all this at Apple without issue. This is we have approval for 1.10 with Apple and offer an SSD stating as such.

Now I want to sort this in the next FW or prove there is an incompatibility with EFi that Apple need to sort out and get an update to you guys.

I don't have the machines you have, i have to rely on what you post to get a fix at least looked into.

[harshw]

Here's the snippet. I had syslog -w running in a terminal. I did a sudo fdisk /dev/disk0 and it froze. I dont think it had anything to do with the fdisk. The problem occured at around 19:46 - 19:49


Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: Hub 0Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: Port 0
Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: bridge-en1: got dev 0x74bc004
Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: bridge-en1: wireless interface detected.
Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: bridge-en1: up
Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: bridge-en1: attached
Apr 10 19:39:26 administrators-macbook kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x8a2b400.
Apr 10 19:39:29 administrators-macbook kernel[0]: WLC_E_COUNTRY_CODE_CHANGED
Apr 10 19:39:29 administrators-macbook kernel[0]: en1: 802.11d country code set to 'AT'.
Apr 10 19:39:29 administrators-macbook kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 5 6 7 8 9 10 11 12 13 1 2 3 4
5 6 7 8 9 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 40 48 56 64 104 112 120 128 136 36 44 52 60 100
Apr 10 19:46:28 administrators-macbook login[2854]: USER_PROCESS: 2854 ttys000
Apr 10 19:46:52 administrators-macbook sudo[2867]: admin : TTY=ttys000 ; PWD=/Users/admin ; USER=root ; COMMAND=/usr/sbin/fdisk /de
v/disk0
Apr 10 19:47:23 administrators-macbook /usr/sbin/spindump[2869]: process 2627 is being monitored
Apr 10 19:50:47 administrators-macbook kernel[0]: PM notification timeout (pid 1012, Yahoo! Messenger)
Apr 10 19:47:29 administrators-macbook /usr/sbin/spindump[2869]: process 2035 is being monitored
Apr 10 19:50:47 administrators-macbook kernel[0]: PM notification timeout (pid 2627, DashboardClient)
Apr 10 19:50:47 administrators-macbook kernel[0]: NVDA::powerStateWillChangeTo(0x71c9000, NVDA, 2 -> 1) timed out after 45158 msApr 10 19:50:47 administrators-macbook kernel[0]: AirPort: Link Down on en1
Apr 10 19:50:12 administrators-macbook ntpd[19]: sendto(17.72.255.11) (fd=22): No route to host
Apr 10 19:50:47 administrators-macbook kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Apr 10 19:50:47 administrators-macbook kernel[0]: NVDA::powerStateWillChangeTo(0x71b7800, NVDA, 2 -> 0) timed out after 45150 ms
Apr 10 19:50:47 administrators-macbook kernel[0]: vmmon: powerStateDidChange flags=0x4 (state 2)
Apr 10 19:50:13 administrators-macbook kernel[0]: System Sleep
Apr 10 19:50:47 administrators-macbook kernel[0]: Wake reason = EC LID0
Apr 10 19:50:47 administrators-macbook kernel[0]: System Wake
Apr 10 19:50:47 administrators-macbook kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 4)
Apr 10 19:50:47 administrators-macbook kernel[0]: Previous Sleep Cause: 5
Apr 10 19:50:47 administrators-macbook kernel[0]: WLC_E_COUNTRY_CODE_CHANGED
Apr 10 19:50:47 administrators-macbook kernel[0]: en1: 802.11d country code set to 'X3'.
Apr 10 19:50:47 administrators-macbook kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140

[Tony]

This is starting to feel like a major issue that I have with eSATA drives connected to MBP, it was a sleep issue. The system was inactive for certain amount of time, the eSATA drive went to sleep, blam there was a freeze in any operations that requires the eSATA drive, like scratch on eSATA or file transfers to eSATA. The only way to actually get it back was to unplug and replug in the eSATA cable.


Did anybody get a freeze while they were working and doing something, or was it during some kind of inactivity no matter how short? so you see this with a non OCZ drive connected as eSATA? we need to be specific

[harshw]

haha ;)

@harshw:

Did i have that sequence right for getting the drive to work again after a hang?

Yup that is the correct sequence :)

[harshw]

This is starting to feel like a major issue that I have with eSATA drives connected to MBP, it was a sleep issue. The system was inactive for certain amount of time, the eSATA drive went to sleep, blam there was a freeze in any operations that requires the eSATA drive, like scratch on eSATA or file transfers to eSATA. The only way to actually get it back was to unplug and replug in the eSATA cable.


Did anybody get a freeze while they were working and doing something, or was it during some kind of inactivity no matter how short?

All the freezes I had were during some activity ... surfing in FireFox, typing in a terminal window etc. I am quite sure that this is related to power management and drive power state changes

SSDs are not HDDs but the ATA and AHCI drivers make deep assumptions that all storage connected to the ATA/AHCI layers has spinning platters ...

[MBHockey]

@harshw

So when it just crashed for you, looking at the log, it happened a few minutes after you had woken it from sleep, correct? It was working fine for a few minutes following waking?

[harshw]

@harshw

So when it just crashed for you, looking at the log, it happened a few minutes after you had woken it from sleep, correct? It was working fine for a few minutes following waking?

It was some 10 - 15 minutes after waking up from sleep.

The previoius crash happened when the macbook wasn't sleeping with the lid down - but clearly was in a low power state with the display off etc.

[MikhailT]

so you see this with a non OCZ drive connected as eSATA? we need to be specific

Yes sorry, I was referring to typical external drives with 500gb-1TB HDD with eSATA interface. (No issue via firewire800/usb)
The reason I mentioned this is that, it is not related to the HDD itself but to the SATA drivers.

Everything tells us that for the wake from sleep issue is related to power state changes/power management.

[MikhailT]

All the freezes I had were during some activity ... surfing in FireFox, typing in a terminal window etc. I am quite sure that this is related to power management and drive power state changes

SSDs are not HDDs but the ATA and AHCI drivers make deep assumptions that all storage connected to the ATA/AHCI layers has spinning platters ...

How can you be sure that it is related to power management if it all occurs during some system activity?

[MBHockey]

It was some 10 - 15 minutes after waking up from sleep.

The previoius crash happened when the macbook wasn't sleeping with the lid down - but clearly was in a low power state with the display off etc.

Just happened to me as well

I put the computer to sleep, woke it, and just like harshw, about 10-12 minutes later my system locked up while web browsing.

I put the lid down, but noticed the 'sleep' light wasn't pulsating (meaning the computer wasn't actually asleep yet). I flipped it over and took out the drive, then replugged it in and woke it, but it was still beach balling. It sat on my desk for a minute, then i put the lid back down and was going to try it again. Except this time I waited. The sleep light was still steady (not sleeping yet) and stayed that way for a couple of minutes. Then boom, sleep light started to pulsate, so I woke it up and all was fine. Things popped back onto the screen and my computer was where I left off.

I had syslog -w running also during the crash. Indeed, like harshw suggested, it seems to not be able to correctly set the power state of the drive (bolded text).

I have no idea why some of the lines output from syslog -w are out of time order...I haven't seen that before. Seems to go back and forth through a tear in the space-time continuum ;)



Fri Apr 10 15:41:43 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 36, configd)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 36, configd)
Fri Apr 10 15:42:42 mikes-macbook ntpd[14] <Error>: sendto(17.151.16.22) (fd=26): Network is down
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 119, Safari)
Fri Apr 10 15:46:01 mikes-macbook mdworker[14492] <Error>: (Error) Import: Importer force killed!
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 13025, DashboardClient)
Fri Apr 10 15:46:58 mikes-macbook ntpd[14] <Error>: sendto(17.151.16.22) (fd=26): Network is down
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: AirPort: Link Down on en1
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: disk0s2: I/O error.
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: jnl: unknown-dev: flushing fs disk buffer returned 0x5
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: AppleAHCIDiskQueueManager::setPowerState(0x43cc500 , 2 -> 0) timed out after 100716 ms
Fri Apr 10 15:43:43 mikes-macbook kernel[0] <Debug>: System Sleep
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: Wake reason = EC LID0
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: System Wake
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: Previous Sleep Cause: 5
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: WLC_E_COUNTRY_CODE_CHANGED
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: en1: 802.11d country code set to 'X0'.
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165 40 48 56 64 104 112 120 128 136 153 161 36 44 52 60
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: NVEthernet::mediaChanged - Link Down
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 36, configd)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 36, configd)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 36, configd)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 24, loginwindow)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 24, loginwindow)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 24, loginwindow)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 119, Safari)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: PM notification timeout (pid 13025, DashboardClient)
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: NVDA::powerStateWillChangeTo(0x47eec00, NVDA, 2 -> 1) timed out after 45157 ms
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: NVDA::powerStateWillChangeTo(0x47efc00, NVDA, 2 -> 0) timed out after 45170 ms
Fri Apr 10 15:47:18 mikes-macbook kernel[0] <Debug>: System Sleep
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: Wake reason = EC LID0
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: System Wake
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: Previous Sleep Cause: 5
Fri Apr 10 15:47:34 mikes-macbook com.apple.launchd[1] (0x10c4d0.mdworker[14492]) <Warning>: Exited with exit code: 1
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: NVEthernet::mediaChanged - Link Down
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: WLC_E_COUNTRY_CODE_CHANGED
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: en1: 802.11d country code set to 'US'.
Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165 40 48 56 64 104 112 120 128 136 153 161 36 44 52 60
Fri Apr 10 15:47:35 mikes-macbook DashboardClient[13025] <Warning>: no upcoming events
Fri Apr 10 15:47:35 mikes-macbook \[0x0-0x7007\].com.apple.dock[96] <Notice>: 2009-04-10 15:47:35.176 DashboardClient\[13025:10b\] no upcoming events
Fri Apr 10 15:47:35 mikes-macbook mDNSResponder[23] <Error>: setsockopt - IP_MULTICAST_IF error 192.168.1.9 -1 errno 49 (Can't assign requested address)
Fri Apr 10 15:47:35 mikes-macbook mDNSResponder[23] <Error>: setsockopt - IP_MULTICAST_IF error 192.168.1.9 -1 errno 49 (Can't assign requested address)
Fri Apr 10 15:47:35 mikes-macbook configd[36] <Notice>: setting hostname to "mikes-macbook.local"
Fri Apr 10 15:47:38 mikes-macbook kernel[0] <Debug>: Auth result for: 00:1f:5b:89:4a:17 MAC AUTH succeeded
Fri Apr 10 15:47:38 mikes-macbook kernel[0] <Debug>: AirPort: Link Up on en1
Fri Apr 10 15:47:41 mikes-macbook configd[36] <Notice>: setting hostname to "mikes-macbook.home"

[harshw]

I have no idea why some of the lines output from syslog -w are out of time order...I haven't seen that before. Seems to go back and forth through a tear in the space-time continuum ;)


When the syslogd thread cant write, it goes to a memory buffer and tries again at some point later. When the write succeeds, it still has the original event timestamp but has been written to the log afterwards. Hence the order is mixed up

Okays I lied. The vertex creates a mini black hole that allows electrons to travel forwards into time :bow: With enough power this black hole can even propel entire laptops through. But no one will believe me hence I stick with the memory buffer story :deviltail

[MBHockey]

It happened again. Another 10-12 minutes after the one I posted about.

It seems much more reproducible this time around. The second time I was unable to revive it, however. Had to do a hard reboot.

I'm going to try to get it to do it again, and make a video, and send it to OCZ with a bow on it :hide:

[harshw]

It happened again. Another 10-12 minutes after the one I posted about.

It seems much more reproducible this time around. The second time I was unable to revive it, however. Had to do a hard reboot.

I'm going to try to get it to do it again, and make a video, and send it to OCZ with a bow on it :hide:

I think OCZ would be happier with logs. Although Apple doesn't like people tampering with its system, OSX is based on Darwin which itself is open source.

Perhaps we can create short instructions on how to get the debug 10.5.6 kernel installed. And then the logs should be more verbose ...

And perhaps I am overly optimistic but if it is a power state issue then these are easily fixed, so it's not all doom and gloom :)

[MBHockey]

how do we send them the logs from mine and your machines of today's crashes?

surely there's something they could take out of those, no?

[harshw]

how do we send them the logs from mine and your machines of today's crashes?

surely there's something they could take out of those, no?

The logs are useful. PM Ryder or Tony (who's still working, on Good Friday, despite telling us he's on holiday) with a link to the posts containing log snippets

And also what steps should be taken to reproduce problem.

For me it is:

Put machine to sleep for 15 mins, wake up, start doing activity and there is a chance that system will randomly freeze in any activity withing 10 - 20 minutes

hence we need "syslog -W 20" running in a background terminal window.

To recover: close lid, wait 2 minutes, unplug drive, plug drive, open lid



The problem could be:

The drive doesn't go out of power saving mode properly because the system doesn't wake it properly

The system gets confused with the drive's power saving methodology

The drive gets confused with the system's power saving request

The system relies on SMART to do power saving and makes lethal assumptions

But I am pretty sure by now it's something to do with power states. Remember that Apple Mac laptops are AGGRESSIVE about power saving unlike Vista/XP. That's how they get that nice battery life.

[MBHockey]

when you close the lid and "wait 2 minutes" are you waiting for the computer to actually go to sleep (pulsating light?)

[harshw]

when you close the lid and "wait 2 minutes" are you waiting for the computer to actually go to sleep (pulsating light?)

Yeah, it doesnt always do that though. Because going to sleep means it has to write info to logs. And it cannot write any info. So I'm just waiting to be on the safe side and make sure that when I remove the drive it's NOT about to go to sleep ;)

[MBHockey]

I see what you're saying. Thanks.

[harshw]

@MBHockey ... did you do a Verify Disk permissions after the lockup ?

[MBHockey]

I didn't until I read your post (but why verify, not repair?):


Verify permissions for “Macintosh HD”
Reading permissions database.
Reading the permissions database can take several minutes.

Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Library/QuickLook/iWork.qlgenerator/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileDeviceHelper.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileSync.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .

Permissions verification complete

[harshw]

I didn't until I read your post (but why verify, not repair?):

Interesting, I have the same output on my machine

Anyways - we had a freeze, closed lid, opened machine, took SSD out, put it back in and presto: filesystem is as good as ever. No corruption, no damage to anything.

Points to the drive either in deep sleep or powered down. And OS X did not panic. It was patiently waiting for the drive to come back to life. If that doesn't point to a deadlock in some AHCI driver code somewhere then I'll eat my hat.

[MBHockey]

Yeah, it seems:


Fri Apr 10 15:47:34 mikes-macbook kernel[0] <Debug>: AppleAHCIDiskQueueManager::setPowerState(0x43cc500 , 2 -> 0) timed out after 100716 ms

Might have been the period of time that the lid was closed but it hadn't started sleeping yet, because it seemed to be around 1-2 minutes (100716 milliseconds = 1 min 40 sec)

[MBHockey]

here's my syslog.conf file:


*.err;kern.*;auth.notice;authpriv,remoteauth,insta ll.none;mail.crit /dev/console
*.notice;authpriv,remoteauth,ftp,install.none;kern .debug;mail.crit /var/log/system.log

# Send messages normally sent to the console also to the serial port.
# To stop messages from being sent out the serial port, comment out this line.
#*.err;kern.*;auth.notice;authpriv,remoteauth.none ;mail.crit /dev/tty.serial

# The authpriv log file should be restricted access; these
# messages shouldn't go to terminals or publically-readable
# files.
auth.info;authpriv.*;remoteauth.crit /var/log/secure.log

lpr.info /var/log/lpr.log
mail.* /var/log/mail.log
ftp.* /var/log/ftp.log
install.* /var/log/install.log
install.* @127.0.0.1:32376
local0.* /var/log/appfirewall.log
local1.* /var/log/ipfw.log

*.emerg *

[masterb]

Same problem here, lock 10-20 min after waking from sleep.
Spec Vertex 120GB fw 1.1, fresh install on a
mbp 17" unibody.
Had problem with 1199 as well.
One other thing i noticed,
is that the permissions allways has errors
like this:


Repairing permissions for “SSD HD”
Reading permissions database.
Reading the permissions database can take several minutes.

Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileDeviceHelper.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileSync.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .

Permissions repair complete

[masterb]

And it happens every time til wakes from sleep !!!

[MBHockey]

And it happens every time til wakes from sleep !!!

What happens every time until it wakes from sleep?

[masterb]

What happens every time until it wakes from sleep?

It locks up after 10-20 min. after every wakeup

[MBHockey]

Mine seems to happen after only some wakeups. I can't reproduce it well.

[harshw]

And it happens every time til wakes from sleep !!!

Can you post logs please ? Keep the following command running in a terminal window



syslog -W 20

OR



tail -f /var/log/system.log

And then when the MBP locks up, make a note of the time, close the lid, open the bottom case, unplug and plug the SSD and then open the lid. The machine should come back to life. At this point check the logs and post anything +/- 2 minutes from the time the machine locked up.

[masterb]

And then when the MBP locks up, make a note of the time, close the lid, open the bottom case, unplug and plug the SSD and then open the lid. The machine should come back to life. At this point check the logs and post anything +/- 2 minutes from the time the machine locked up.

I have the 17" so I have to unscrew 10 screws to open the button case.. Might try it later....

[MBHockey]

@harshw,

I want to thank you for bringing the Ram issue to my attention. I returned the ram to crucial since I have been running the stock ram for a few days without any of the issues i was seeing before.

Now i've just got to make myself swallow my pride and order the 4gb from Apple ;)

[harshw]

@harshw,

I want to thank you for bringing the Ram issue to my attention. I returned the ram to crucial since I have been running the stock ram for a few days without any of the issues i was seeing before.

Now i've just got to make myself swallow my pride and order the 4gb from Apple ;)

Apple 4GB is fine. Sell the stock 2GB on ebay AFTER you have confirmed that the Apple 4GB works fine (which is why BTO is the best)

Or you could ask Tony or Ryder about the upcoming OCZ MacBook RAM.

The problem with non Apple RAM was that the EFI/BIOS relied on some arcane SPD settings and these were never really published, hence third party RAM was not configured properly by the laptop

Vendors who are aware of these issues have proper SPD settings in their RAM and everything seems to work fine with these RAM chips.

[Tony]

I'm not 100&#37; sure hence I will ask but from memory our Apple qualified memory does have the SPD support needed.

what you see on the OCZ site regards Apple qualified memory means we have been to apple and it has been tested with Apple

[MBHockey]

Gotcha.

No worries guys, I actually ordered the 4 GB from Apple as soon as Crucial approved my RMA for refund request (which was prior to harshw's post).

Now, back on topic...
:yup:

[jerry]

For $730 I expect it to work without the minute to minute fear that the machine could go down at any instant. That's not "bleeding edge"; that's broken.

I agree. I thought this drive was ready for mainstream use, that's why I chose it. I didn't realize I would end up as a beta tester. My time is too valuable to be troubleshooting problems for OCZ for no pay, I have enough other problems of my own that don't pay! ;)

Sadly, I had to pull the Vertex and go back to spinning glass. Good luck narrowing this down guys. I'll buy another Vertex when this is all sorted out, because I too would rather spend my money with smaller more innovative companies.

-Jerry

[MBHockey]

It's one thing to be a beta tester for a company that is unresponsive, but quite another to help out a company who is willing to put in the level of support that OCZ is demonstrating.

I think this whole "testing" thing will turn out to be quite an asset. I mean, think of the problems you encounter on a computer. Little, minute, esoteric problems that if you brought up to a big company they wouldn't think twice about ignoring you.

At least here, in this public forum, we can bring to light such issues and then in time expect firmware upgrades to resolve them. I doubt there are absolutely no issues with an SSD like the Intel. There's just no public forum run by intel to diagnose and fix the smaller (but yet still annoying) issues.

[AppleUser]

Did you fresh install to the drive?

Each time I've restore from Time Machine. This doesn't clone but does a file level restore so doesn't get affected by the clone issues.

[Tony]

It's one thing to be a beta tester for a company that is unresponsive, but quite another to help out a company who is willing to put in the level of support that OCZ is demonstrating.

I think this whole "testing" thing will turn out to be quite an asset. I mean, think of the problems you encounter on a computer. Little, minute, esoteric problems that if you brought up to a big company they wouldn't think twice about ignoring you.

At least here, in this public forum, we can bring to light such issues and then in time expect firmware upgrades to resolve them. I doubt there are absolutely no issues with an SSD like the Intel. There's just no public forum run by intel to diagnose and fix the smaller (but yet still annoying) issues.

I agree here...the best way of helping is to involve the community using the product

[AppleUser]

I wonder if it's possible to configure the System.log to be on a separate device; either by reconfiguring the path from the standard /var/log/System.log to /myotherdevmountpoint/log/System, or, replacing with a soft link/mount. In that way if OSX does fail to write to the Vertex it can still write the timeout/error to the logfile which can be recovered later.
Then the log could either be a flash stick for example.

[MBHockey]

That's what harshw was saying a few pages ago. Sure seems like a good idea to me, but I'm not knowledgeable enough to know how to actually implement that.

[harshw]

That's what harshw was saying a few pages ago. Sure seems like a good idea to me, but I'm not knowledgeable enough to know how to actually implement that.

All you have to do is change the entries in syslog.conf to point to the path of either the flash stick - /Media/USB1/logs/system.log instead of /var/logs/system.log (if the stick is mounted there, confirm with Disk Utility) or use an @ sign followed by the hostname of a remote computer running syslogd

Your Mac OSX runs standard FreeBSD Unix :)

[MBHockey]

Thanks harshw. Got it going to my external USB drive, but obviously, I can't get the thing to hang again to get some output.

I'm sure the system will go down later when I have forgotten about it and actually need to use it :)

[harshw]

Hi all

To everyone having problems on Macs with lockups and freezes ... how many are using Parallels or VMWare Fusion ?

I'm using Fusion 2.0

[MBHockey]

I haven't reinstalled Parallels yet after the v1.10 flash and I still had lockups

[harshw]

Hmm. Red herring then.

[MBHockey]

I had another lockup late last night but unfortunately I couldn't revive the machine (after 10 minutes of hot plugging and trying to make it sleep, it wouldn't come back). There was no text in the system.log on my external USB relevant to the time frame when the computer went down.

This one was similar to one I had last week - upon activating Dashboard my computer hard locked. The only non-Apple widget I'm running is iStat Pro (I don't see how Dashboard could be really causing this).

Has anyone else had problems going into Dashboard?

[harshw]

I had another lockup late last night but unfortunately I couldn't revive the machine (after 10 minutes of hot plugging and trying to make it sleep, it wouldn't come back). There was no text in the system.log on my external USB relevant to the time frame when the computer went down.

This one was similar to one I had last week - upon activating Dashboard my computer hard locked. The only non-Apple widget I'm running is iStat Pro (I don't see how Dashboard could be really causing this).

Has anyone else had problems going into Dashboard?

I had one lockup after going into Dashboard. But it's not reproducible :( In fact nothing is reproducible with this error. But no lockups so far ...

[MBHockey]

Tough to reproduce indeed.

I need my computer to be pretty stable this week, so I'm just not going to sleep it at all. Hopefully OCZ got some useful info from the log I posted earlier.

[Tony]

I have instructed Indilinx to look hard at sleep and wake commands to the drive, under OSX.
That's about all I can suggest to them at this time.

[MBHockey]

very much appreciated, Tony.

[Tony]

have in mind using Intel chipsets under XP and Vista is works pretty much 100&#37; ok now with FW1.10...so it may be an OSX issue over a FW issue. There is only so much can be done with FW...but i have asked them to focus in this area.

[vasu]

have in mind using Intel chipsets under XP and Vista is works pretty much 100% ok now with FW1.10...so it may be an OSX issue over a FW issue. There is only so much can be done with FW...but i have asked them to focus in this area.

What about with nvidia chipsets under xp and vista?

[MBHockey]

have in mind using Intel chipsets under XP and Vista is works pretty much 100% ok now with FW1.10...so it may be an OSX issue over a FW issue. There is only so much can be done with FW...but i have asked them to focus in this area.

Yeah, I understand that. But without knowing what the underlying cause is we cannot know who is responsible for a fix. Since the issue is happening on every Mac with a Vertex (I haven't heard about this problem with other SSDs on MacOS X), it seems it'd be at least up to Indilinx/OCZ to explain WHY this is happening (which I am really hoping they can do!).

At least then we'll all have a better idea of who should be responsible for a fix.

[MikhailT]

have in mind using Intel chipsets under XP and Vista is works pretty much 100% ok now with FW1.10...so it may be an OSX issue over a FW issue. There is only so much can be done with FW...but i have asked them to focus in this area.

Unibody uses nvidia chipsets, pre-unibody uses intel chipsets. Just thought you should know that.

[ybakos]

I've also been witnessing this issue. 250GB Vertex. MacBook Pro 3,1 (non-unibody). Been a user for about two weeks.

My machine will lock up right after I wake from sleep. I'll open the lid, the screen will appear as usual, but once I start using an app it hangs; I can then cmd-tab to other apps, but then they also hang. Then I can't do anything other than power down.

[ybakos]

Has anyone here started a thread at Apple support or submitted a bug? Please post the link. I'll do the same.

[ybakos]

I've started a thread here at the apple forums, although I don't expect much activity...

http://discussions.apple.com/thread.jspa?threadID=1975606&tstart=0

I've also submitted a consumer 'feebdack' via http://www.apple.com/feedback/macosx.html

I'm not sure if the ADC bug tracker is the best way to get attention about this issue or not.

[FieryFurnace]

... Since the issue is happening on every Mac with a Vertex...

I don't think you can say every Mac with a Vertex has this issue.
I am using my Vertex 60GB (fw 1199) for 4 weeks without any problems, and I have my MB running around 6-10 hours a day with sleeping it 3-4 times a day.

[AppleUser]

(fw 1199) for 4 weeks

You brave man..

[drops]

I have a 120 GB APEX in a 4.1 MBP. I have the same problems coming out of hibernation. Since I pmset -a 0 and don't allow power management to send SDD to sleep I've had no crashes or freezes.

There seems to be a specific lock-up problem if you install the system yourself from dvd. Leopard 10.5.5 that came with the system does not even recognize the drive. A retail Leopard 10.5.5 sees the drive, but I got the first freeze already during setup when I was taking the picture for the account.

The only way I got an uptodate OSX 10.5.6 was to have a working 10.5.6 be imaged onto the APEX. Apple support told me that SSDs are only supported since 10.5.2, but I get them impression that OSX 10.5.6 only "tolerates" OCZ SSDs and will only work with the mentioned tweaks. There's probably a firmware update or OSX update necessary to get full hibernation support.

This diskpart method does not apply to OSX, does it? I heard that OSX will align the partion anyway to 4K. Is this correct?

kind regards
Oliver Drobnik

[MBHockey]

I don't think you can say every Mac with a Vertex has this issue.
I am using my Vertex 60GB (fw 1199) for 4 weeks without any problems, and I have my MB running around 6-10 hours a day with sleeping it 3-4 times a day.

which Mac do you have?

[FieryFurnace]

which Mac do you have?

See my "Rig Specs" on the left, a 2008 white MacBook with Intel ICH8-M.
All original except the Vertex and 4GB memory.

[MBHockey]

Ah, sorry I should have thought of that :o

Interesting. I wonder if any other older MacBook owners are having an issue.

Maybe it's an nVidia --> Vertex problem? (I think that's the motherboard the Unibodies use...?)

[mlord]

have in mind using Intel chipsets under XP and Vista is works pretty much 100% ok now with FW1.10...so it may be an OSX issue over a FW issue. There is only so much can be done with FW...but i have asked them to focus in this area.

One thing that could help narrow this down, would be to run Linux on the Macbook, and see if the problems can be reproduced without OSX installed.

If yes, then it points to a hardware (or EFI) issue.
If not, the results are inconclusive.

Cheers

[MBHockey]

What I really don't understand is the delay.

Why, if OS X can't set the power level correctly, would the drive lock up 15 minutes after it has woken?

What is the significance of the delay? Does OS X routinely do something 10-15 minutes to a drive after it is awoken from sleep that might cause this?

Why wouldn't it just happen as soon as it's woken up?

[harshw]

One thing that could help narrow this down, would be to run Linux on the Macbook, and see if the problems can be reproduced without OSX installed.

If yes, then it points to a hardware (or EFI) issue.
If not, the results are inconclusive.

Cheers

Agreed

I'm planning on installing Ubuntu on my MacBook, can't seem to get the time ( I know I know ... 10 minute job ... ) so that I can test both ext4/trim and also see if the sleep/wake issue is present

The problem is that most linuxes, Ubuntu included, seem to have a great deal of difficulty with power states on the Macs, ie they run a lot hotter than normal. Hence I was waiting till someone solved the fans/smc/idle throttling issues, didn't want to cook my Macbook :)

[Tony]

What I really don't understand is the delay.

Why, if OS X can't set the power level correctly, would the drive lock up 15 minutes after it has woken?

What is the significance of the delay? Does OS X routinely do something 10-15 minutes to a drive after it is awoken from sleep that might cause this?

Why wouldn't it just happen as soon as it's woken up?

Is the drive awake or is OSX running within ram and then hangs when it can't access the drive?

[MBHockey]

I'm really not sure.

:waits for harshw to chime in:

:chit: