Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nope. 2.8GHz Mac Pro here with the 2600HD, and it did the graphic corruption freeze about 5 minutes after installing both 10.5.2 and the Leopard Graphics Update.

Yeah, same things for me... 2 weeks and os x update later, Mac Pro 2008 still unusable, many thanks apple!

Jules
 
Nope. 2.8GHz Mac Pro here with the 2600HD, and it did the graphic corruption freeze about 5 minutes after installing both 10.5.2 and the Leopard Graphics Update.

Yeah, same things for me... 2 weeks and os x update later, Mac Pro 2008 still unusable, many thanks apple!

Jules

Same thing here. Had my system freeze up 5 minutes after updates.

Oh man, that's not good. My replacement machine was doing well until yesterday when I installed 10.5.2 and the graphics update. It's not as bad as it was before, but now I get weird things like when you scroll up and down in Safari or in any other program like Quickbooks, text disappears and when I scroll back and forth it reappears. At least my system doesn't freeze though - yet.
 
Well I finally got my new system with the 8800GT card and it's all just fine so far :)
 
Damnit! I really want a Mac Pro. But I'm afraid to buy because of this issue. I don't want to spend the extra cash on the 8800, but I also don't want a machine that freezes. It has to work perfectly, especially considering the enormous price tag.
 
For those of you having the freeze issues. Can you please monitor your system.log and post any suspicious messages that happened around the time of your crash. There are MANY people with this ATI 2600 issue at the Mac Pro Apple discussions and the current theory is that it's a video card issue. Many are reporting kernel/GPU messages in system.log.
 
For those of you having the freeze issues. Can you please monitor your system.log and post any suspicious messages that happened around the time of your crash. There are MANY people with this ATI 2600 issue at the Mac Pro Apple discussions and the current theory is that it's a video card issue. Many are reporting kernel/GPU messages in system.log.

How's this for suspicious. Yesterday night, not long after I'd first booted up after the 10.5.2 update, and the Leopard Graphics Update.

Code:
Feb 12 17:18:00 Isako kernel[0]: ** Device in slot: SLOT-1 **
Feb 12 17:18:00 Isako kernel[0]: ** GPU Debug Info Start **
Feb 12 17:18:00 Isako kernel[0]: 0x01019588 000090a2 00009588 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x0011a010 00000000 00000000 00a6106b
Feb 12 17:18:00 Isako kernel[0]: 0x00f8fc00 00000001 00000001 00008a12
Feb 12 17:18:00 Isako kernel[0]: 0x80028241 00028182 00000000 00004000
Feb 12 17:18:00 Isako kernel[0]: 0x0a03800a 000000e0 00000020 00000200
Feb 12 17:18:00 Isako kernel[0]: 0x0050005a 01300130 01600160 00b800b8
Feb 12 17:18:00 Isako kernel[0]: 0x00e000e0 002d002d 20000000 00100f0d
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 10000000 00001550 00001900
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 8f300101 00000000 00121303
Feb 12 17:18:00 Isako kernel[0]: 0x00492491 00000000 00000000 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000010 a0003030 00000003 00100010
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 000003ff 200000c0 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 c0000000 00000000 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 44c83d57 00000001 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00100130 00000017 00000000 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00003005 00000000 660ee616 00100010
Feb 12 17:18:00 Isako kernel[0]: 0x00000f23 00000f00 00000001 00777474
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 00000000 00000000 00a030e0
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 00000000 00000000 10000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000001 00000000 00000000 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x00000000 00000000 00000020 00008008
Feb 12 17:18:00 Isako kernel[0]: 0x00000200 00000000 00007fe0 00000000
Feb 12 17:18:00 Isako kernel[0]: 0x000000a0 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 e400000d 403c003c
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 040404b4 00400040 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00006052 00000008 00100026 00003c2d
Feb 12 17:18:01 Isako kernel[0]: 0x00003c2d 00003c2e 00003c00 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00008000 00000000 000028c0
Feb 12 17:18:01 Isako kernel[0]: 0x000000a0 001002e1 00003102 00085800
Feb 12 17:18:01 Isako kernel[0]: 0x00008008 00000120 0000000a 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000002 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000008 00100026 00003c14 00003c14
Feb 12 17:18:01 Isako kernel[0]: 0x00003c16 00003c00 00000003 00300013
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00200026 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000400 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00180000 04002001 3f7f7f3f
Feb 12 17:18:01 Isako kernel[0]: 0x40004000 00012000 1d000000 aaaa5555
Feb 12 17:18:01 Isako kernel[0]: 0x00000000 00000000 00000000 00000000
Feb 12 17:18:01: --- last message repeated 11 times ---
Feb 12 17:18:01 Isako kernel[0]: 0x3a736e6c
Feb 12 17:18:01 Isako kernel[0]: 0xc0306a00
Feb 12 17:18:01 Isako kernel[0]: 0xc0046a00
Feb 12 17:18:01 Isako kernel[0]: 0xc0076d00
Feb 12 17:18:01 Isako kernel[0]: 0xc0012d00
Feb 12 17:18:01 Isako kernel[0]: 0xc0046a00
Feb 12 17:18:01 Isako kernel[0]: 0xc0076d00
Feb 12 17:18:01 Isako kernel[0]: 0xc0005300
Feb 12 17:18:01 Isako kernel[0]: 0x3a736e6c
Feb 12 17:18:01 Isako kernel[0]: 0xc0306a00
Feb 12 17:18:01 Isako kernel[0]: 0:0x0000a2a4
Feb 12 17:18:01 Isako kernel[0]: 1:0x00000016
Feb 12 17:18:01 Isako kernel[0]: 2:0x00002010
Feb 12 17:18:01 Isako kernel[0]: 3:0x00020000
Feb 12 17:18:01 Isako kernel[0]: 4:0x0000217d
Feb 12 17:18:01 Isako kernel[0]: 5:0xffffffff
Feb 12 17:18:01 Isako kernel[0]: 6:0x0000217c
Feb 12 17:18:01 Isako kernel[0]: 7:0x09800000
Feb 12 17:18:01 Isako kernel[0]: 8:0x0000217e
Feb 12 17:18:01 Isako kernel[0]: 9:0x00000000
Feb 12 17:18:01 Isako kernel[0]: 10:0xc0053c00
Feb 12 17:18:01 Isako kernel[0]: 11:0x00000003
Feb 12 17:18:01 Isako kernel[0]: 12:0x0000217f
Feb 12 17:18:01 Isako kernel[0]: 13:0x00000000
Feb 12 17:18:01 Isako kernel[0]: 14:0x00000000
Feb 12 17:18:01 Isako kernel[0]: 15:0x80000000
Feb 12 17:18:01 Isako kernel[0]: 16:0x0000000a
Feb 12 17:18:01 Isako kernel[0]: 17:0xc0023200
Feb 12 17:18:01 Isako kernel[0]: 18:0x11af9040
Feb 12 17:18:01 Isako kernel[0]: 19:0x00000000
Feb 12 17:18:01 Isako kernel[0]: 20:0x00004cb0
Feb 12 17:18:01 Isako kernel[0]: 21:0x0000a2a4
Feb 12 17:18:01 Isako kernel[0]: 22:0x00000016
Feb 12 17:18:01 Isako kernel[0]: 23:0x00002010
Feb 12 17:18:01 Isako kernel[0]: 24:0x00020000
Feb 12 17:18:01 Isako kernel[0]: 25:0x00002140
Feb 12 17:18:01 Isako kernel[0]: 26:0x00006054

Maybe I'm being a little quick at drawing conclusions, but I think it might have something to do with the GPU. Like, in Slot 1. Where my video card is.

I can attach the 524KB text file that's full of this kind of crap, if you'd like. Yes... 524KB of what's above, ad infinausem. In a timespan of two minutes before I hit the power button.
 
How's this for suspicious. Yesterday night, not long after I'd first booted up after the 10.5.2 update, and the Leopard Graphics Update.

[snip]

Maybe I'm being a little quick at drawing conclusions, but I think it might have something to do with the GPU. Like, in Slot 1. Where my video card is.

I can attach the 524KB text file that's full of this kind of crap, if you'd like. Yes... 524KB of what's above, ad infinausem. In a timespan of two minutes before I hit the power button.

That's the same error I had when my 2600XT had problems. I'd try to get a replacement if I were you, those problems surely will not go away by themselves. Could be EFI, could be leopard, could be hardware, who knows... :(
 
That's the same error I had when my 2600XT had problems. I'd try to get a replacement if I were you, those problems surely will not go away by themselves. Could be EFI, could be leopard, could be hardware, who knows... :(

It's definitely hardware. I'm running Vista via Boot Camp on a separate drive, and Vista has this nifty thing where it stops and restarts the graphics driver after the graphics driver hangs or crashes. Every PC system I've seen it do that on has either had a bad video card, or in the case of onboard PC graphics, a bad motherboard. It does it on mine, as well.
 
I'm getting my Mac Pro tomorrow. It's being delivered tomorrow that is. I surely hope there is no issues with it. I've already returned one. I have the 8800GT in the new one though!
 
It's definitely hardware. I'm running Vista via Boot Camp on a separate drive, and Vista has this nifty thing where it stops and restarts the graphics driver after the graphics driver hangs or crashes. Every PC system I've seen it do that on has either had a bad video card, or in the case of onboard PC graphics, a bad motherboard. It does it on mine, as well.

Does Boot Camp use Apple or ATI supplied drivers for the ATI card? If the drivers in Boot Camp were developed by Apple then there is still a possibility that the problem is due to buggy drivers. Having said that, the problem certainly looks like a timing problem that is either due to a faulty IC or overheating (which leads to timing problems).
 
Does Boot Camp use Apple or ATI supplied drivers for the ATI card? If the drivers in Boot Camp were developed by Apple then there is still a possibility that the problem is due to buggy drivers. Having said that, the problem certainly looks like a timing problem that is either due to a faulty IC or overheating (which leads to timing problems).

No - you can install regular AMD or nVidia drivers in bootcamp - you don't have to use the one that came with Apple. I did and I don't have an issue with the driver.
 
Does Boot Camp use Apple or ATI supplied drivers for the ATI card? If the drivers in Boot Camp were developed by Apple then there is still a possibility that the problem is due to buggy drivers. Having said that, the problem certainly looks like a timing problem that is either due to a faulty IC or overheating (which leads to timing problems).

The Boot Camp drivers may be Apple supplied, but it's ATI who made them. Regardless of which, I replaced them with later versions, anyways - so I strongly doubt that it's just a driver issue. I have a 20" Al iMac that's been rock solid from the get go, and they're both using the same drivers under OS X now that the 10.5.2 and Leopard Graphics Updates are out.
 
To those affected:

How much GBs of memory do you have installed?
Did you add your own memory? And if yes, how much?

Background is I've added 4 GB myself to get to 6 GB of main memory and experienced the issue quite a lot. I've now removed the 4 GB and am stress-testing the machine. It would be quite nice to know about your memory configuration.

Thanks a lot!
 
So what's the latest on this? Still totally unresolved? They offer to exchange your machine but chances are you might get another defective one?

I'll be calling apple tomorrow and any current info would be much appreciated. Would rather not:

*have to drag the MP down there

*have to wait for a replacement


Thanks!
 
I am so sick of having my machine freeze up I can't stand it.

I'm skeptical, however, of the video card explanation. Nor do I want the hassle of returning the machine.

What to do??
 
The machine's been running rock solid for 13h now after I removed the RAM. This is pretty confusing though, as the RAM passed the AHT test with zero errors. Also, I get the debug info for the gfx card in the log *and* mine has a "good" P/N (the S/N exceeds the ones presented by far - it really seems to be a running number).

Still, it would be very interesting to know whether others have added RAM themselves or whether they experience the problem with stock Apple RAM.

Please share that piece of information. It'd be most appreciated on my end.
 
The machine's been running rock solid for 13h now after I removed the RAM. This is pretty confusing though, as the RAM passed the AHT test with zero errors. Also, I get the debug info for the gfx card in the log *and* mine has a "good" P/N (the S/N exceeds the ones presented by far - it really seems to be a running number).

Still, it would be very interesting to know whether others have added RAM themselves or whether they experience the problem with stock Apple RAM.

Please share that piece of information. It'd be most appreciated on my end.

I experienced it with stock Apple ram and third party ram, so that eliminates that. My replacement machine is better, I wouldn't call it rock solid, but better. At least this time around it's not freezing/locking up. The graphics is kinda funky now though since I installed 10.5.2 and the latest graphics update right after. I'd say it didn't fix much and probably almost broke something.
 
Thanks! The stock Mac Pro with freshly installed OS and updates (graphics + 10.5.2) and no additional apps or hardware installed did just crash.

Called Apple and asked for a replacement. They agreed. Let's hope the replacement machine will be more reliable.

After all, this can't be a problem affecting all customers as we'd sure have read about these problems in tests and reviews as well.

My personal conclusion after 2 days of experimenting and reading numerous discussions is that this is a graphics card hardware / firmware problem. I'll let you know, if the replacement machine should be faulty, too (I don't expect it before 2 weeks from now, though).
 
Has it been confirmed that installing an 8800 solves the problem?

I need to get back to work!
 
Are these all still 2600XT problems or 8800GT problems too? I have an 8800GT and I have no problems...
 
To those affected:

How much GBs of memory do you have installed?
Did you add your own memory? And if yes, how much?

Background is I've added 4 GB myself to get to 6 GB of main memory and experienced the issue quite a lot. I've now removed the 4 GB and am stress-testing the machine. It would be quite nice to know about your memory configuration.

Thanks a lot!

I had the problem with stock two gigs of RAM. If you think your RAM is an issue, it's easy to boot from the install CD and run the full memory test. You should always do that anyway with new RAM.
 
I had the problem with stock two gigs of RAM. If you think your RAM is an issue, it's easy to boot from the install CD and run the full memory test. You should always do that anyway with new RAM.

Thanks for the info. I've been able to reproduce the problem with both stock memory and additional memory. I've also already done the tests and they passed with zero errors. As you said you "had" the problem - what was the solution in your case?

Generally:

I do believe that this is a rare issue as in "maybe about 5% affected" as otherwise there'd be a HUGE outcry. And all I've found on the subject is this forum thread any one on Apple discussions, while all the mainstream media have had positive reports on how much faster the gfx have gotten with 10.5.2. They'd have reported about issues for sure, if they had had them in the weeks they already use the 8 core Mac Pros.

So I don't believe it to be a general driver issue, but is likely just a batch of faulty gfx cards. *crosses fingers*
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.