Ticket Options
Question Details
TICKET ARCHIVE -> Infinite Loops
myopic4141 - Jun 4, 2005 - 8:06 pm
The system hangs in an infinite loop repeating the same sound when playing music with interrupts locked out forcing a cold start.
DeltaMac - Jun 4, 2005 - 8:16 pm
What are you doing at the time that sound begins to play?
Is it part of a game - or some other type of software - or a song played through iTunes
Or, another music app of some kind. (What software are you using, be specific)
- Dale
Is it part of a game - or some other type of software - or a song played through iTunes
Or, another music app of some kind. (What software are you using, be specific)
- Dale
myopic4141 - Jun 4, 2005 - 9:16 pm
I am playing a tune in iTunes 4.8 or Player Pro 5.9 running on MacOS 10.3.9. Just listening to the music and nothing else. The system is a Quicksilver w/ PowerLogix 1.4 GHz G4 (7457), 1.5 GB RAM, and Radeon 9000.
DeltaMac - Jun 4, 2005 - 9:27 pm
Update your PlayerPro software? version 5.9.8 is current, and looks like some new updates may be showing up sometime, there's very recent info at the web site (June 2005) saying 5.9.9 may be showing up soon.
Is this always the same song? I would guess not, but correct me...
If you have to do a full reset to get the system going again, you should, first stop, open your Console, and check the logs for the approximate time of the crash, looking for any pertinent info that might help. This could give you errors in completely different software (like QuickTime?)
Do you have lockups of any other kind, outside of music playing?
Can you describe what external hardware you have attached to your G4?
- Dale
Is this always the same song? I would guess not, but correct me...
If you have to do a full reset to get the system going again, you should, first stop, open your Console, and check the logs for the approximate time of the crash, looking for any pertinent info that might help. This could give you errors in completely different software (like QuickTime?)
Do you have lockups of any other kind, outside of music playing?
Can you describe what external hardware you have attached to your G4?
- Dale
myopic4141 - Jun 5, 2005 - 12:12 am
Canon S600 printer, ViewSonic VE170b display, Apple 15" flat screen, Plantronic USB headset (it goes dead when the sound quits), DLink 604 router, DLink DCM-201 cable modem. I verified it was not the USB headset by removing it and switching to the built in audio.
It is different musical items from both iTunes and PlayerPro (5.9.8 and there will be no further updates).
I have reviewed the console logs and they do not tell me anything at the time of hanging. I have had a periodic panics resulting from Data Access (0x300), Instruction access (0x400), and one Uncorrectable machine check errors. The panic logs show that the machine is in a sad state when the panics occur.
All program crashes are EXC_BAD_ACCESS exceptions. I have tested and retested memory using memtest and it tells me the memory is okay. I am suspecting an ISR handling problem regarding the audio; but, do not know how to go after ISR's under MacOS X.
I have not had the same problem under MacOS 9; but, do not run the same programs.
It is different musical items from both iTunes and PlayerPro (5.9.8 and there will be no further updates).
I have reviewed the console logs and they do not tell me anything at the time of hanging. I have had a periodic panics resulting from Data Access (0x300), Instruction access (0x400), and one Uncorrectable machine check errors. The panic logs show that the machine is in a sad state when the panics occur.
All program crashes are EXC_BAD_ACCESS exceptions. I have tested and retested memory using memtest and it tells me the memory is okay. I am suspecting an ISR handling problem regarding the audio; but, do not know how to go after ISR's under MacOS X.
I have not had the same problem under MacOS 9; but, do not run the same programs.
DeltaMac - Jun 5, 2005 - 3:52 pm
If you like the Player Pro software, I think you should take a look at this page :
http://sourceforge.net/forum/forum.php?forum_id=470564
this is the late info I was talking about.
have you tried downloading and installing the 10.3.9 combined updater?
Reinstalling this combined updater on top of your present system is a known fix for a variety of problems that might develop after a system upgrade. Be sure to repair disk permissions after installing the combined update.
The EXC_BAD_ACCESS really doesn't tell very much, but further down the log you will see a crashed thread, and that will sometimes give a better clue about what causes a crash.
Hope some of this will help you -
- Dale
http://sourceforge.net/forum/forum.php?forum_id=470564
this is the late info I was talking about.
have you tried downloading and installing the 10.3.9 combined updater?
Reinstalling this combined updater on top of your present system is a known fix for a variety of problems that might develop after a system upgrade. Be sure to repair disk permissions after installing the combined update.
The EXC_BAD_ACCESS really doesn't tell very much, but further down the log you will see a crashed thread, and that will sometimes give a better clue about what causes a crash.
Hope some of this will help you -
- Dale
myopic4141 - Jun 5, 2005 - 8:28 pm
I have installed MacOS 10.3.9 twice and replaced the motherboard.
What I am looking for is a way to monitor interrupts like Macsbug could do so I can pinpoint what is causing the problem.
What I am looking for is a way to monitor interrupts like Macsbug could do so I can pinpoint what is causing the problem.
DeltaMac - Jun 5, 2005 - 9:36 pm
If you would show more of your crash log, which is what OS X uses to record information concerning a system or app crash, then that could help more than anything to determine the cause.
There is no software that I am aware of, that does a similar function to MacsBug. I think this is because OS X records that sort data in the logs, and there would be little to gain by allowing access to interupts, however unlikely that a low level hardware call would be useful.
Lockups or system freezes typically are related to:
Marginal memory (Some memory works great with OS 9 and older OS X, until Panther. Now, OS X can be very balky with out-of-spec memory) memtest is a really good utility for testing memory.
Malfunctioning or not well-supported PCI cards (tried removing any that you have?) Tried running on just a single monitor through the AGP vid card?
Marginal USB hubs (do you have one? have you tried running with out that?)
Failing processor...
Marginal FireWire drives
Have you ever tried to SSH into your system to try to kill a stuck process? (please don't ask me about this, I don't know what's involved, I just know this is a common 'un-sticking' procedure that many people use successfully, if you have network access from another computer.
This is a very convoluted post, only because the type of problem you have can be very frustrating to troubleshoot, and sometimes you come across a cure by accident, so I'm throwing lots of different directions your way, Maybe something will help. Where to start? Start with the memory... Did you replace any memory at the time you replaced the logic board?? Take a lot of memory out, leaving maybe 512MB, to see if there is any change.
I think you can see there's no quick fixes - unless you have some luck....
- Dale
There is no software that I am aware of, that does a similar function to MacsBug. I think this is because OS X records that sort data in the logs, and there would be little to gain by allowing access to interupts, however unlikely that a low level hardware call would be useful.
Lockups or system freezes typically are related to:
Marginal memory (Some memory works great with OS 9 and older OS X, until Panther. Now, OS X can be very balky with out-of-spec memory) memtest is a really good utility for testing memory.
Malfunctioning or not well-supported PCI cards (tried removing any that you have?) Tried running on just a single monitor through the AGP vid card?
Marginal USB hubs (do you have one? have you tried running with out that?)
Failing processor...
Marginal FireWire drives
Have you ever tried to SSH into your system to try to kill a stuck process? (please don't ask me about this, I don't know what's involved, I just know this is a common 'un-sticking' procedure that many people use successfully, if you have network access from another computer.
This is a very convoluted post, only because the type of problem you have can be very frustrating to troubleshoot, and sometimes you come across a cure by accident, so I'm throwing lots of different directions your way, Maybe something will help. Where to start? Start with the memory... Did you replace any memory at the time you replaced the logic board?? Take a lot of memory out, leaving maybe 512MB, to see if there is any change.
I think you can see there's no quick fixes - unless you have some luck....
- Dale
myopic4141 - Jun 7, 2005 - 12:38 am
I will have to look up SSH. Nothing hooked up to the fire wire. I ran memtest and did all kinds of memory swaps using 1M (2 512K chips). The only PCI card is the Ultra-Tek133P+ to run drives greater than 130 GB and the AGP card is a Radeon 9000. There is nothing on the fire wire.
I can send the panic logs and some of the crash logs if you wish; but, it has been a while since a crash and then something has already been hosed elsewhere with the sound device locked out.
I am pretty sure it has something to do with the sound device handler or it may be in the hardware interface. I do not see any information on that anywhere.
I can send the panic logs and some of the crash logs if you wish; but, it has been a while since a crash and then something has already been hosed elsewhere with the sound device locked out.
I am pretty sure it has something to do with the sound device handler or it may be in the hardware interface. I do not see any information on that anywhere.
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
