Re: [Sound-open-firmware] How to debug rare DSP crashes (moving discussion over from GH)
Replying now, after I have added traces within platform_panic I *do not* see them (also back on the default config I seem to have caused it to fail within first playthrough; it's also luck based with the timing). Will try tomorrow to also add prints in the agent itself and turn off other extra traces (so I don't get *too* much spam in the etrace buffer).
I had written trace_error in there, which should have added the error within the etrace buffer I believe.
-----Original Message----- From: Sound-open-firmware sound-open-firmware-bounces@alsa-project.org On Behalf Of Paul Olaru Sent: Monday, October 28, 2019 2:22 PM To: sound-open-firmware@alsa-project.org; Lauda, Tomasz tomasz.lauda@intel.com Cc: Jerome Laclavere jerome.laclavere@nxp.com; Daniel Baluta daniel.baluta@nxp.com; Guido Roncarolo guido.roncarolo@nxp.com Subject: [Sound-open-firmware] How to debug rare DSP crashes (moving discussion over from GH)
Moving the discussion from https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com... over to this list.
In summary, whenever I have the system agent enabled and at default values, after two or three continuous playthroughs (depending on which timer I use as the platform timer, for the most part) of the same song (with duration 17:06) I get a complete freeze (with verbose traces enabled I see no more activity in the trace mailbox, not even the WFX/WFE which are essentially flooding the trace mailbox during normal function) and no signs of panic (I'm going to test now with a trace added in platform_panic; currently this function is empty).
Disabling the system agent helps, changing CONFIG_SYSTICK_PERIOD to 2000 also helps. And I hear no glitch at all during the playthroughs with either of these changes applied (although a 1ms or smaller glitch once in 30 minutes is probably unnoticeable by any human ear is it?)
How should I continue with this?
I'll come back and mention if there is a panic or the freeze comes from something else. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.al...
Added an extra trace in the agent and now I can see indeed there is something.
I see that there is in fact a panic triggered by an agent. delta is computed as 1332551 in that case which would be more than the panic limit. CPU frequency 16 MHz.
ticks_per_msec seems to be set to 666000 for the CPU, so about 2ms when the panic occurred (this last one occurred unusually fast actually, possibly because of the extra traces within the agent itself maybe).
-----Original Message----- From: Sound-open-firmware sound-open-firmware-bounces@alsa-project.org On Behalf Of Paul Olaru Sent: Monday, October 28, 2019 3:33 PM To: sound-open-firmware@alsa-project.org; Lauda, Tomasz tomasz.lauda@intel.com Cc: Daniel Baluta daniel.baluta@nxp.com; Jerome Laclavere jerome.laclavere@nxp.com; Guido Roncarolo guido.roncarolo@nxp.com Subject: Re: [Sound-open-firmware] How to debug rare DSP crashes (moving discussion over from GH)
Replying now, after I have added traces within platform_panic I *do not* see them (also back on the default config I seem to have caused it to fail within first playthrough; it's also luck based with the timing). Will try tomorrow to also add prints in the agent itself and turn off other extra traces (so I don't get *too* much spam in the etrace buffer).
I had written trace_error in there, which should have added the error within the etrace buffer I believe.
-----Original Message----- From: Sound-open-firmware sound-open-firmware-bounces@alsa-project.org On Behalf Of Paul Olaru Sent: Monday, October 28, 2019 2:22 PM To: sound-open-firmware@alsa-project.org; Lauda, Tomasz tomasz.lauda@intel.com Cc: Jerome Laclavere jerome.laclavere@nxp.com; Daniel Baluta daniel.baluta@nxp.com; Guido Roncarolo guido.roncarolo@nxp.com Subject: [Sound-open-firmware] How to debug rare DSP crashes (moving discussion over from GH)
Moving the discussion from https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com... over to this list.
In summary, whenever I have the system agent enabled and at default values, after two or three continuous playthroughs (depending on which timer I use as the platform timer, for the most part) of the same song (with duration 17:06) I get a complete freeze (with verbose traces enabled I see no more activity in the trace mailbox, not even the WFX/WFE which are essentially flooding the trace mailbox during normal function) and no signs of panic (I'm going to test now with a trace added in platform_panic; currently this function is empty).
Disabling the system agent helps, changing CONFIG_SYSTICK_PERIOD to 2000 also helps. And I hear no glitch at all during the playthroughs with either of these changes applied (although a 1ms or smaller glitch once in 30 minutes is probably unnoticeable by any human ear is it?)
How should I continue with this?
I'll come back and mention if there is a panic or the freeze comes from something else. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.al... _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.al...
participants (1)
-
Paul Olaru