Screen won't turn on after sleep for newest macbook pro (Feb 26 2011)

Question

Hi!
I just bought the 13' Macbook Pro with an 2.7GHz dual-core i7 processor and 500GB of space, the $1500 model. I am having a problem with the screen and I am wondering if I should be worried about it or if anyone else has noticed it. If it continues, I will have to take it into the store and see if I can get it fixed.
My macbooks screen will not turn on after it falls asleep for a long period of time. The first night I had this computer, it was playing music and I turned the screen brightness all the way down/off and then I fell asleep. The energy settings were set so that the computer would fall asleep after 20 minutes. Pathfinder, F.lux and iTunes were the only application running at the time. When I woke up the next morning, the light on the computer's side indicating it was asleep was slowly fading in and out (as expected). I hit some keys on the keyboard and the keyboards backlighting turned on after a few seconds.
But the screen did not turn on. I tried adjusting the screen brightness on the keyboard and nothing happened. After a few minutes, I held down the power button and heard the computer turn off. I turned the computer back on, AND THE SCREEN LOOKED VERY STRANGE. I could see part of iTunes fragmented/segmented into 5 or 6 sections across the screen. There were also strange lines going across the screen. It looked kind of like a leftover image of iTunes that could be solved with a screen refresh. I turned off my computer again and turned it back on about two more times, and then the screen would simple just not turn on.
As I was packing up to go to the Apple Store, I tried one more time to turn my computer on and the screen was working fine. This was yesterday, and for the rest of the day the computer seemed to work fine. However, I don't think I let my computer fall asleep all day yesterday because I was using it so much.
Basically the same thing happened this morning when I woke up, except to a lesser degree. My computers screen was unresponsive after keyboard input, but I was able to get music to play from my speakers. I restarted it and it seems to be working fine. I didn't see the screen do that weird fragmentation thing this time.
I think something about the sleep function is interfering with my computer's screen. Or perhaps Pathfinder or F.lux have something to do with it. F.lux, by the way, is a application that turns the screen a dark yellowish at night to help your eyes. But I have friends that use this application and I myself have used it for a while and we have never had this problem. Then again, none of them have a 13 inch with an i7.
Does anyone know about this problem and have advice that would save me a trip to the Apple store?
thanks!

Answer 1

Bad news and good news. The bad news is that it happened again this morning. The good news is that I finally found something interesting in the console log, at the exact second my clock is stuck when the machine is failing to wake from sleep:
3/10/11 7:33:53 AM kernel WaitForStamp: Overflowed waiting for stamp 0x32b5d on Blit ring: called from wait for blt buffer (2D blt)
3/10/11 7:33:53 AM kernel timestamp = 0x32b5c
3/10/11 7:33:53 AM kernel ** Debug info for apparent hang in Blit graphics engine **
3/10/11 7:33:53 AM kernel ring head = 0x000013b0, wrap count = 0x 0
3/10/11 7:33:53 AM kernel ring tail = 0x00001f58 ring control = 0x00003401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x004 4KB pages
3/10/11 7:33:53 AM kernel timestamps = 0x32b5c
3/10/11 7:33:53 AM kernel Semaphore register values:
3/10/11 7:33:53 AM kernel VRSYNC: (0x12044) = 0x0
3/10/11 7:33:53 AM kernel BRSYNC: (0x22040) = 0x0
3/10/11 7:33:53 AM kernel RVSYNC: (0x 2040) = 0x0
3/10/11 7:33:53 AM kernel BVSYNC: (0x22044) = 0x0
3/10/11 7:33:53 AM kernel RBSYNC: (0x 2044) = 0x0
3/10/11 7:33:53 AM kernel VBSYNC: (0x12040) = 0x0
3/10/11 7:33:53 AM kernel trying to clear semaphore wait on Blit ring
3/10/11 7:33:53 AM kernel After attempt to clear semaphor wait = 0x00003001 no longer waiting
3/10/11 7:33:53 AM kernel kIPEHR: 0x1800001
3/10/11 7:33:53 AM kernel kINSTDONE: 0xffffffff
3/10/11 7:33:53 AM kernel kINSTDONE_1: 0x3fffffff
From when the problem apparently starts (some point in the night while my machine is idle and supposedly asleep) until when I discover it and reboot the machine, I get dozens or hundreds of the above messages. Now somebody just needs to figure out what that means and stop it from happening...