Periodically, I get kernel panics or system failures that end up waiting for a remote debugger connection and the system is unresponsive from that point on. I do not have a second system for a remote connection; but, do have a dual cpu system. Is there a way to designate the second cpu as the remote connection? If not, could anyone tell me which module handles the remote connection setup so that I might determine if such a connection can be established?
Dual 1.7 G4 GHz QuickSilver,
Mac OS X (10.4.11),
1.5 G RAM, triple monitor
Is there some older OS stuff on there? I thought that message went out about 10.3 or so, now you should get a message in many languages saying KP you must restart.
I would like to find out what the problem is as well which is why I asked if the module handling the fault could use the other cpu as the debugger cpu. I had done that on other multiprocessor systems and wonder if it is possible here. According to the upgrade manufacturer, the interrupt lines go to both cpu's.
With certain tools you can disable one CPU, but if you van do what you're thinking is either way beyond me or not possible.
Have you booted off the Install Disk by holding the *d key* down at boot-up, (not the c key), and run the extended Apple HW Test? Some Install disks require holding the Option key at bootup to select the AHT. Some Macs came with separate AHT CDs.
Here's the list and downloads for AHT for G4s if you don't have it...
I have upgraded my system with a Newer Technology dual 1.73 GHz PowerPC G4 (MPC-7448) which results in an scc_/3/7 error when running the Apple Hardware test. This appears to be common to all third party cpu upgrades. I would need to know what an scc_/3/7 error is, what test detected the error, and a copy of the module that performs the test to determine if such an error actually exist or it is just a factor of using a third party upgrade. There is not a lot of information about the AHT to review.
In regards to using a second cpu for debugging, that is not beyond my capability if such a thing is possible. I just need to know what modules perform the communications link so that I can review them.
I originally got the window message that BDAqua posted regarding restarting the computer. That first happened about a week ago, so after reading on these forums I put in the Hardware Test CD that came with my eMac and ran that, and it didn't detect any errors. So then the next time I get on the computer this same message doesn't come up, but a new one that says:
Waiting for remote debugger connection, system failure, latest crash info...
I can't remember all it said, it was a lot, but that was some of it. Can anyone help me out on what is going on here. I know I have an older computer, but really don't want to have to get a new one if I can avoid it.
I'm not doing anything specific when this happens. Usually just have a few programs open and either looking on the internet or using Quicken or some program like that which doesn't take a lot of RAM. Because this computer is older and doesn't run very fast I usually only use it for minimal things.
Do you think that by blowing the dust out of the computer this will help "fix" the messages that I am getting about restarting my computer and waiting for remote debugger connections.
I actually think this should stay under this thread as I am having the same problems as the original post. Thanks for all your help.
I'll have to pay more attention to when it happens. There are some times when I get on the computer that it doesn't happen at all, and then other times it rears its ugly head. I'll keep closer tabs on when it happens and I'll let you know.
I already have the full developer suite installed which includes the latest CHUD for Tiger.
Yesterday, I ran memtest in single user mode (memtest all 5 -L) without changing the memory configuration and all tests passed for the 5 runs. I then swapped the lower and upper banks followed by another run of memtest (memtest all 5 -L) in single user mode. This time, I encountered errors with some arithmetic functions in the middle bank for one of the five runs (the other 4 ran without error).