@andrewabernathy Yeah, I think that’s how you have to do it. :-(
@danielpunkass Could be. The odd thing is that for me it didn’t get bad until 10.7.3 (IIRC).
@danielpunkass Both AppleCare and the local provider assured me they had the exact same tools and diagnostics.
@danielpunkass I guess it’s worth a shot when it’s convenient and this is no longer my main Mac.
@danielpunkass So they think my problem is a software issue, and I tend to agree—it matches the driver bug others are seeing since Lion.
@danielpunkass After escalating, I got the local authorized service provider to do the full diagnostic hardware test, which the Mac passed.
@danielpunkass AppleCare (more than one guy) treated it as random Internet hearsay. Had me reboot twice and told me it was all fixed.
@danielpunkass You would think so from reading that, but I haven’t even been able to get AppleCare to acknowledge that page exists.