That's quite interesting since I'm experiencing exactly the same behavour with my brand new 160GB X-25M with an unibody MacBook Pro under MacOS. Everything is fine for hours and suddendly the disk stops responding. In some cases this will last for about 15 seconds and afterwards everything is fine again. What makes it really a problem is that these situations are repeating more and more frequently rendering the system unsusable.
Restarting does not really help. It takes time. Yesterday evening it was completely unusable. I powered it off over night. This morning everything is working great - probably not long...
Ok, I think I've discovered the issue here. For whatever reason some chipsets seem to struggle with this (and other) SSD's. Apparently Command Queuing (or NCQ) tends to be the culprit here. First I assume you have the latest chipset/IDE/SATA/etc. drivers installed as that should be step number one. After that in Windows Vista & 7 RC1 I was able to simply go into Device Manger --> IDE ATA/ATAPI controllers --> NVIDIA nForce Serial ATA Controller --> Properties, for the controller that's running my SSD, then uncheck the "Enable command queuing" checkbox. After a reboot I no longer see th is problem. Now, to actually install Windows I was forced to copy the contents of the "sata_ide" portion of the IDE folder of the latest nForce drivers (just extract/install them on an existing PC to gain access to them, or goto nVidia's website as they have a walkthrough on the download page for the drivers in PDF form) to a floppy. Then during the windows install utilizing F6 I was able to piont to the disk and have Windows setup use them on the install. That seemed to get me by until Windows made its first boot which is when I was able to make the change above. I'm sure you could make the change automatic with a littler driver config/ini work.
Nevertheless I've had no problems since disabling command queuing so I highly recommend this as a solution to this issue, although it's obviously not an ideal one as you should be able to leave CQ enabled.
Ok, I contacted Intel support regarding my problem. The answer is posted below. For those who don't speak German, here is a rough summary:
Intel seems to be aware of certain problems regarding the compatibility between Intel SSDs and nVidia chipsets. However, they refuse any support with the note, that one could not guarantee compatibility with all chipsets. The staff member adviced me to contact Apple. Great idea.
Sehr Geehrter Herr ...,
Vielen dank für Ihrer Rückgabe.
Leider sind wir nicht in der lage dieses problem zu unterstutzen.
Offensichtlich wird dieses problem verursacht durch inkompatibilität zwischen den Intel SSD und Ihr Macbook,
dieses problem wurde anscheinend nicht behoben durch ein neuer Firmware version.
Leider kann Intel nicht garantieren daß die Intel SSD's mit alle systemen oder Komponente von anderen Hersteller einwandfrei funktionieren.
So können Wir auch nicht garantieren daß komponente von anderen hersteler immer einwandfrei funktionieren mit Intel Motherboards.
Apple soll Sie informieren bezüglich Kompatibilät bezüglich dieses problems.
Wir bedauren Sie nicht anders informieren zu können.
Für weitere Fragen stehe ich Ihnen gerne zur Verfügung.
Mit freundlichen Grüssen
I don't give up that fast although I'm a bit disappointed by Intel. Ok, they are not directly responsible for the problem but concealing problems one is aware of isn't a good practice...
For the time being: Which nVidia Chipset do you use? Has it onboard graphics? If yes, do you use it?
I searched the web especially for problems regarind the X25-M and the unbody MacBooks - nothing. On the other hand there are a few reports that everything should works fine. Since I had similar (worse) problems with an OCZ Vertex hard disk I'm very sure that the drive itself is perfectly fine. At the moment I'm experimenting with settings I have influence on - e.g. disabling the onboard VGA. Furthermore it seems that the problems are arise more quickly if I'm operating on big files (e.g. Virtual Machines running or File Vault activated).