Still Without Laptop
I got the Powerbook back last week (very impressive three day turnaround), but as soon as I started trying to use it for anything important it would start to crash randomly. Different applications would exit unexpectadly, the computer would freeze up, a couple of times the whole machine just rebooted. Examining some of the crash reports I saw what looked like numerous memory violations and access errors. I tried taking the extra RAM out and things still crashed, so it looks like the new “logic board” they installed was kaput from the start. Called up AppleCare and they suggested what I expected they would, a re-install.
Archive and Install crashed halfway through, so then the machine wouldn’t even boot up. A completely fresh install completed successfully, but the system still kept crashing (in more predictable ways this time at least). When I called AppleCare back they immediately bumped me up to a Product Specialist since it was my fourth call on the issue. They pretty much immediately said, “send it back.” They were going to send me out a shipping box but instead I just wandered over to the local Apple Store (lucky to work a few blocks away) and went through the whole diagnostic process with the “Genius” there. Finally he wrote up a work tag and accepted it to send back.
What I found funny about the whole process was that even though I gave him multiple stack traces that pointed to some pretty specific memory problems, his descriptions of all the crashes in the trouble ticket were simply “kernel panics.” When I pointed this out he told me that pretty much any system-destabilizing crash is wrapped under the umbrella term “kernel panic.” Having a long background in Unix development, I found this rather funny. I guess Apple has really taken the whole make-Unix-friendly tact to the extreme.
Comments(0)