All,
Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.
As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
Please let me know if you have any questions or concerns.
While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.
Kind regards, Paul
Hi Paul,
1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”
1. We still have a very slow boot up time (+2minutes).
1. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.
As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.
I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.
I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.
Thanks, Kim
From: Paul Neuhardt paul.neuhardt@linaro.org Sent: Friday, November 4, 2022 7:05 AM To: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Project Status and Burn Report
All,
Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.
As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
Please let me know if you have any questions or concerns.
While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.
Kind regards, Paul -- [Linaro]http://www.linaro.org/ Paul Neuhardt | Sr. Program Manager T: +44 0771 377 8664 paul.neuhardt@linaro.orgmailto:glen.valante@linaro.org IRC: pneuhardt
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner < kim.steiner@sightlineapplications.com> wrote:
Hi Paul,
- In an email to Dmitry on 11/2/2022, I informed him that the gpu
temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”
We still have a very slow boot up time (+2minutes).
I informed Dmitry that the glxgears application only runs for a few
minutes before stopping.
As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.
I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.
I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.
Thanks,
Kim
*From:* Paul Neuhardt paul.neuhardt@linaro.org *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org *Subject:* [Sightlineapplications] Project Status and Burn Report
All,
Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.
As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
Please let me know if you have any questions or concerns.
While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.
Kind regards,
Paul
--
[image: Linaro] http://www.linaro.org/
*Paul Neuhardt* | *Sr. Program Manager*
T: +44 0771 377 8664 paul.neuhardt@linaro.org glen.valante@linaro.org IRC: pneuhardt
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and Burn Report____ __ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed. ____ __ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward. Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
1) I was able to reproduce the failure during the cold boot. I'm investigating it now.
2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPU then.”____ __ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
1) I was able to reproduce the failure during the cold boot. I'm investigating it now.
2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively - add more warming up sources to the CPU and GPU devices - add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns. ____ __ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
I was out of the office on Friday but I will run our normal test today. Glxgears had been failing at room temperature for me after a few minutes. I will try glxgears again with your instruction from serial console if it doesn't work. I may also be using the 4.14 filesystem on the DB but I remember trying the 5.15 filesystem and glxgears still did not work for me.
Speaking of the filesystem, we would like to keep using the 4.14 filesystem when we switch to the 5.15 kernel. Do you see any issue with that? Penguin Solutions is also asking about which rootfs to use. Please advise.
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively - add more warming up sources to the CPU and GPU devices - add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively - add more warming up sources to the CPU and GPU devices - add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now. "
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now. "
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
On 21/11/2022 16:05, Kim Steiner wrote:
Hi Dmitry,
I was out of the office on Friday but I will run our normal test today. Glxgears had been failing at room temperature for me after a few minutes. I will try glxgears again with your instruction from serial console if it doesn't work. I may also be using the 4.14 filesystem on the DB but I remember trying the 5.15 filesystem and glxgears still did not work for me.
Speaking of the filesystem, we would like to keep using the 4.14 filesystem when we switch to the 5.15 kernel. Do you see any issue with that? Penguin Solutions is also asking about which rootfs to use. Please advise.
I have been using our old release while testing the kernel for you, so using the old filesystem should be fine.
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time (+2minutes).____ __ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status and BurnReport____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
Also, would it be possible for me to get your boot.img to compare with the one I built?
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time(+2minutes).____
__ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status andBurn Report____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi. How would I go about adding CONFIG_GPIO_SYSFS to the configuration? I tried adding this to the db820c_defconfig file, but it doesn't show up in the .config when I build.
Also, if I want to build the kernel modules to go into the \lib\modules\ directory on the board, do I just add modules to this command:
make -C ../kernel O=$(pwd) ARCH=arm64 Image.gz dtbs -j $(nproc)
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, November 28, 2022 12:20 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
Also, would it be possible for me to get your boot.img to compare with the one I built?
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote:
Kim,
I had thought that the latest updates had been posted to your repository. My apologies for the misunderstanding. I will ask Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
Paul
On Fri, 4 Nov 2022 at 14:31, Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> wrote:
Hi Paul,____ __ __ 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu temp issue may not be fixed. He stated “Thank you for the test. I'll work on improving the warming of the CPU/GPUthen.”____
__ __ 2. We still have a very slow boot up time(+2minutes).____
__ __ 3. I informed Dmitry that the glxgears application only runs for a few minutes before stopping.____ __ __ __ __ As of Wednesday (with latest git repository changes), the above issues existed and I do not plan on doing any more testing until I see new changes or get something new to test.____ __ __ I will inform Penguin Solutions that you are close so they can work on patches for us to apply to our custom board build.____ __ __ I would also like to again request a clear set of build instructions (changes to .config, compiler, initram…) so that I can build/test correctly.____ __ __ Thanks,____ Kim____ __ __ *From:* Paul Neuhardt <paul.neuhardt@linaro.org <mailto:paul.neuhardt@linaro.org>> *Sent:* Friday, November 4, 2022 7:05 AM *To:* sightlineapplications@lists.linaro.org <mailto:sightlineapplications@lists.linaro.org> *Subject:* [Sightlineapplications] Project Status andBurn Report____
__ __ All,____ __ __ Dmitry has now delivered what he believes to be the final set of updates to Sightline in support of this project. Sightline is in the process of testing these deliverables and we expect that the results will be at or close to what was expected. If there are still gaps, we will of course work to close them.____ __ __ As of today, there are still 13.5 hours of Dmitry's time left available under the most recent contract extension. This should provide adequate time for any consultation needed and any updates and/or final tuning necessary. I have attached a brief report on that burn to this email. Steve, I will send you a more detailed version that you can share inside Sightline as needed.
__ __ Please let me know if you have any questions or concerns.
__ __ While I will continue to be in touch as we close down the project, I want to take this opportunity to thank everyone involved for all their work. I am confident I speak for all of us at Linaro when I say I hope we have the opportunity to work with Sightline Applications again in the future.____ __ __ Kind regards,____ Paul____ -- ____ Linaro <http://www.linaro.org/>____ *Paul Neuhardt*|/Sr. Program Manager/____ T: +44 0771 377 8664 paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> IRC: pneuhardt____ __ __
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
On 30/11/2022 18:47, Kim Steiner wrote:
Hi. How would I go about adding CONFIG_GPIO_SYSFS to the configuration? I tried adding this to the db820c_defconfig file, but it doesn't show up in the .config when I build.
This required also enabling CONFIG_EXPORT. I have pushed the config change to enable this option.
Also, if I want to build the kernel modules to go into the \lib\modules\ directory on the board, do I just add modules to this command:
make -C ../kernel O=$(pwd) ARCH=arm64 Image.gz dtbs -j $(nproc)
I'm attaching the updated build instructions document, which includes the necessary changes (see #5a).
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, November 28, 2022 12:20 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
Also, would it be possible for me to get your boot.img to compare with the one I built?
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote: > Kim, > > I had thought that the latest updates had been posted to your > repository. My apologies for the misunderstanding. I will ask > Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
> > Paul > > On Fri, 4 Nov 2022 at 14:31, Kim Steiner > <kim.steiner@sightlineapplications.com > mailto:kim.steiner@sightlineapplications.com> wrote: > > Hi Paul,____ > > __ __ > > 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu > temp issue may not be fixed. He stated “Thank you for the test. > I'll work on improving the warming of the CPU/GPU > then.”____ > > __ __ > > 2. We still have a very slow boot up time > (+2minutes).____ > > __ __ > > 3. I informed Dmitry that the glxgears application only runs for a > few minutes before stopping.____ > > __ __ > > __ __ > > As of Wednesday (with latest git repository changes), the above > issues existed and I do not plan on doing any more testing until I > see new changes or get something new to test.____ > > __ __ > > I will inform Penguin Solutions that you are close so they can work > on patches for us to apply to our custom board build.____ > > __ __ > > I would also like to again request a clear set of build instructions > (changes to .config, compiler, initram…) so that I can build/test > correctly.____ > > __ __ > > Thanks,____ > > Kim____ > > __ __ > > *From:* Paul Neuhardt <paul.neuhardt@linaro.org > mailto:paul.neuhardt@linaro.org> > *Sent:* Friday, November 4, 2022 7:05 AM > *To:* sightlineapplications@lists.linaro.org > mailto:sightlineapplications@lists.linaro.org > *Subject:* [Sightlineapplications] Project Status and > Burn Report____ > > __ __ > > All,____ > > __ __ > > Dmitry has now delivered what he believes to be the final set of > updates to Sightline in support of this project. Sightline is in the > process of testing these deliverables and we expect that the results > will be at or close to what was expected. If there are still gaps, > we will of course work to close them.____ > > __ __ > > As of today, there are still 13.5 hours of Dmitry's time left > available under the most recent contract extension. This should > provide adequate time for any consultation needed and any > updates and/or final tuning necessary. I have attached a brief > report on that burn to this email. Steve, I will send you a more > detailed version that you can share inside Sightline as needed. > ____ > > __ __ > > Please let me know if you have any questions or concerns. > ____ > > __ __ > > While I will continue to be in touch as we close down the project, I > want to take this opportunity to thank everyone involved for all > their work. I am confident I speak for all of us at Linaro when I > say I hope we have the opportunity to work with Sightline > Applications again in the future.____ > > __ __ > > Kind regards,____ > > Paul____ > > -- ____ > > Linaro http://www.linaro.org/____ > > > > *Paul Neuhardt*|/Sr. Program Manager/____ > > T: +44 0771 377 8664 > paul.neuhardt@linaro.org mailto:glen.valante@linaro.org > IRC: pneuhardt____ > > __ __ > > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote: > Kim, > > I had thought that the latest updates had been posted to your > repository. My apologies for the misunderstanding. I will ask > Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
> > Paul > > On Fri, 4 Nov 2022 at 14:31, Kim Steiner > <kim.steiner@sightlineapplications.com > mailto:kim.steiner@sightlineapplications.com> wrote: > > Hi Paul,____ > > __ __ > > 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu > temp issue may not be fixed. He stated “Thank you for the test. > I'll work on improving the warming of the CPU/GPU > then.”____ > > __ __ > > 2. We still have a very slow boot up time > (+2minutes).____ > > __ __ > > 3. I informed Dmitry that the glxgears application only runs for a > few minutes before stopping.____ > > __ __ > > __ __ > > As of Wednesday (with latest git repository changes), the above > issues existed and I do not plan on doing any more testing until I > see new changes or get something new to test.____ > > __ __ > > I will inform Penguin Solutions that you are close so they can work > on patches for us to apply to our custom board build.____ > > __ __ > > I would also like to again request a clear set of build instructions > (changes to .config, compiler, initram…) so that I can build/test > correctly.____ > > __ __ > > Thanks,____ > > Kim____ > > __ __ > > *From:* Paul Neuhardt <paul.neuhardt@linaro.org > mailto:paul.neuhardt@linaro.org> > *Sent:* Friday, November 4, 2022 7:05 AM > *To:* sightlineapplications@lists.linaro.org > mailto:sightlineapplications@lists.linaro.org > *Subject:* [Sightlineapplications] Project Status and > Burn Report____ > > __ __ > > All,____ > > __ __ > > Dmitry has now delivered what he believes to be the final set of > updates to Sightline in support of this project. Sightline is in the > process of testing these deliverables and we expect that the results > will be at or close to what was expected. If there are still gaps, > we will of course work to close them.____ > > __ __ > > As of today, there are still 13.5 hours of Dmitry's time left > available under the most recent contract extension. This should > provide adequate time for any consultation needed and any > updates and/or final tuning necessary. I have attached a brief > report on that burn to this email. Steve, I will send you a more > detailed version that you can share inside Sightline as needed. > ____ > > __ __ > > Please let me know if you have any questions or concerns. > ____ > > __ __ > > While I will continue to be in touch as we close down the project, I > want to take this opportunity to thank everyone involved for all > their work. I am confident I speak for all of us at Linaro when I > say I hope we have the opportunity to work with Sightline > Applications again in the future.____ > > __ __ > > Kind regards,____ > > Paul____ > > -- ____ > > Linaro http://www.linaro.org/____ > > > > *Paul Neuhardt*|/Sr. Program Manager/____ > > T: +44 0771 377 8664 > paul.neuhardt@linaro.org mailto:glen.valante@linaro.org > IRC: pneuhardt____ > > __ __ > > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Thanks Dmitry!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:12 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 30/11/2022 18:47, Kim Steiner wrote:
Hi. How would I go about adding CONFIG_GPIO_SYSFS to the configuration? I tried adding this to the db820c_defconfig file, but it doesn't show up in the .config when I build.
This required also enabling CONFIG_EXPORT. I have pushed the config change to enable this option.
Also, if I want to build the kernel modules to go into the \lib\modules\ directory on the board, do I just add modules to this command:
make -C ../kernel O=$(pwd) ARCH=arm64 Image.gz dtbs -j $(nproc)
I'm attaching the updated build instructions document, which includes the necessary changes (see #5a).
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, November 28, 2022 12:20 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
Also, would it be possible for me to get your boot.img to compare with the one I built?
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote: > Kim, > > I had thought that the latest updates had been posted to your > repository. My apologies for the misunderstanding. I will ask > Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
> > Paul > > On Fri, 4 Nov 2022 at 14:31, Kim Steiner > <kim.steiner@sightlineapplications.com > mailto:kim.steiner@sightlineapplications.com> wrote: > > Hi Paul,____ > > __ __ > > 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu > temp issue may not be fixed. He stated “Thank you for the test. > I'll work on improving the warming of the CPU/GPU > then.”____ > > __ __ > > 2. We still have a very slow boot up time > (+2minutes).____ > > __ __ > > 3. I informed Dmitry that the glxgears application only runs for a > few minutes before stopping.____ > > __ __ > > __ __ > > As of Wednesday (with latest git repository changes), the above > issues existed and I do not plan on doing any more testing until I > see new changes or get something new to test.____ > > __ __ > > I will inform Penguin Solutions that you are close so they can work > on patches for us to apply to our custom board > build.____ > > __ __ > > I would also like to again request a clear set of build instructions > (changes to .config, compiler, initram…) so that I can build/test > correctly.____ > > __ __ > > Thanks,____ > > Kim____ > > __ __ > > *From:* Paul Neuhardt <paul.neuhardt@linaro.org > mailto:paul.neuhardt@linaro.org> > *Sent:* Friday, November 4, 2022 7:05 AM > *To:* sightlineapplications@lists.linaro.org > mailto:sightlineapplications@lists.linaro.org > *Subject:* [Sightlineapplications] Project Status and > Burn Report____ > > __ __ > > All,____ > > __ __ > > Dmitry has now delivered what he believes to be the final set of > updates to Sightline in support of this project. Sightline is in the > process of testing these deliverables and we expect that the results > will be at or close to what was expected. If there are still gaps, > we will of course work to close them.____ > > __ __ > > As of today, there are still 13.5 hours of Dmitry's time left > available under the most recent contract extension. This should > provide adequate time for any consultation needed and any > updates and/or final tuning necessary. I have attached a brief > report on that burn to this email. Steve, I will send you a more > detailed version that you can share inside Sightline as needed. > ____ > > __ __ > > Please let me know if you have any questions or concerns. > ____ > > __ __ > > While I will continue to be in touch as we close down the project, I > want to take this opportunity to thank everyone involved for all > their work. I am confident I speak for all of us at Linaro when I > say I hope we have the opportunity to work with Sightline > Applications again in the future.____ > > __ __ > > Kind regards,____ > > Paul____ > > -- ____ > > Linaro http://www.linaro.org/____ > > > > *Paul Neuhardt*|/Sr. Program Manager/____ > > T: +44 0771 377 8664 > paul.neuhardt@linaro.org mailto:glen.valante@linaro.org > IRC: pneuhardt____ > > __ __ > > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote: > Kim, > > I had thought that the latest updates had been posted to your > repository. My apologies for the misunderstanding. I will ask > Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
> > Paul > > On Fri, 4 Nov 2022 at 14:31, Kim Steiner > <kim.steiner@sightlineapplications.com > mailto:kim.steiner@sightlineapplications.com> wrote: > > Hi Paul,____ > > __ __ > > 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu > temp issue may not be fixed. He stated “Thank you for the test. > I'll work on improving the warming of the CPU/GPU > then.”____ > > __ __ > > 2. We still have a very slow boot up time > (+2minutes).____ > > __ __ > > 3. I informed Dmitry that the glxgears application only runs for a > few minutes before stopping.____ > > __ __ > > __ __ > > As of Wednesday (with latest git repository changes), the above > issues existed and I do not plan on doing any more testing until I > see new changes or get something new to test.____ > > __ __ > > I will inform Penguin Solutions that you are close so they can work > on patches for us to apply to our custom board > build.____ > > __ __ > > I would also like to again request a clear set of build instructions > (changes to .config, compiler, initram…) so that I can build/test > correctly.____ > > __ __ > > Thanks,____ > > Kim____ > > __ __ > > *From:* Paul Neuhardt <paul.neuhardt@linaro.org > mailto:paul.neuhardt@linaro.org> > *Sent:* Friday, November 4, 2022 7:05 AM > *To:* sightlineapplications@lists.linaro.org > mailto:sightlineapplications@lists.linaro.org > *Subject:* [Sightlineapplications] Project Status and > Burn Report____ > > __ __ > > All,____ > > __ __ > > Dmitry has now delivered what he believes to be the final set of > updates to Sightline in support of this project. Sightline is in the > process of testing these deliverables and we expect that the results > will be at or close to what was expected. If there are still gaps, > we will of course work to close them.____ > > __ __ > > As of today, there are still 13.5 hours of Dmitry's time left > available under the most recent contract extension. This should > provide adequate time for any consultation needed and any > updates and/or final tuning necessary. I have attached a brief > report on that burn to this email. Steve, I will send you a more > detailed version that you can share inside Sightline as needed. > ____ > > __ __ > > Please let me know if you have any questions or concerns. > ____ > > __ __ > > While I will continue to be in touch as we close down the project, I > want to take this opportunity to thank everyone involved for all > their work. I am confident I speak for all of us at Linaro when I > say I hope we have the opportunity to work with Sightline > Applications again in the future.____ > > __ __ > > Kind regards,____ > > Paul____ > > -- ____ > > Linaro http://www.linaro.org/____ > > > > *Paul Neuhardt*|/Sr. Program Manager/____ > > T: +44 0771 377 8664 > paul.neuhardt@linaro.org mailto:glen.valante@linaro.org > IRC: pneuhardt____ > > __ __ > > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote:
Hi Dmitry and Paul, Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
Thank you, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Thursday, November 10, 2022 3:34 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
Thanks, Kim -----Original Message----- From: Kim Steiner Sent: Friday, November 4, 2022 9:49 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt paul.neuhardt@linaro.org Cc: sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 4, 2022 8:03 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 04/11/2022 17:39, Paul Neuhardt wrote: > Kim, > > I had thought that the latest updates had been posted to your > repository. My apologies for the misunderstanding. I will ask > Dmitry to post his updates as soon as possible.
The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc.
> > Paul > > On Fri, 4 Nov 2022 at 14:31, Kim Steiner > <kim.steiner@sightlineapplications.com > mailto:kim.steiner@sightlineapplications.com> wrote: > > Hi Paul,____ > > __ __ > > 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu > temp issue may not be fixed. He stated “Thank you for the test. > I'll work on improving the warming of the CPU/GPU > then.”____ > > __ __ > > 2. We still have a very slow boot up time > (+2minutes).____ > > __ __ > > 3. I informed Dmitry that the glxgears application only runs for a > few minutes before stopping.____ > > __ __ > > __ __ > > As of Wednesday (with latest git repository changes), the above > issues existed and I do not plan on doing any more testing until I > see new changes or get something new to test.____ > > __ __ > > I will inform Penguin Solutions that you are close so they can work > on patches for us to apply to our custom board > build.____ > > __ __ > > I would also like to again request a clear set of build instructions > (changes to .config, compiler, initram…) so that I can build/test > correctly.____ > > __ __ > > Thanks,____ > > Kim____ > > __ __ > > *From:* Paul Neuhardt <paul.neuhardt@linaro.org > mailto:paul.neuhardt@linaro.org> > *Sent:* Friday, November 4, 2022 7:05 AM > *To:* sightlineapplications@lists.linaro.org > mailto:sightlineapplications@lists.linaro.org > *Subject:* [Sightlineapplications] Project Status and > Burn Report____ > > __ __ > > All,____ > > __ __ > > Dmitry has now delivered what he believes to be the final set of > updates to Sightline in support of this project. Sightline is in the > process of testing these deliverables and we expect that the results > will be at or close to what was expected. If there are still gaps, > we will of course work to close them.____ > > __ __ > > As of today, there are still 13.5 hours of Dmitry's time left > available under the most recent contract extension. This should > provide adequate time for any consultation needed and any > updates and/or final tuning necessary. I have attached a brief > report on that burn to this email. Steve, I will send you a more > detailed version that you can share inside Sightline as needed. > ____ > > __ __ > > Please let me know if you have any questions or concerns. > ____ > > __ __ > > While I will continue to be in touch as we close down the project, I > want to take this opportunity to thank everyone involved for all > their work. I am confident I speak for all of us at Linaro when I > say I hope we have the opportunity to work with Sightline > Applications again in the future.____ > > __ __ > > Kind regards,____ > > Paul____ > > -- ____ > > Linaro http://www.linaro.org/____ > > > > *Paul Neuhardt*|/Sr. Program Manager/____ > > T: +44 0771 377 8664 > paul.neuhardt@linaro.org mailto:glen.valante@linaro.org > IRC: pneuhardt____ > > __ __ > > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Image
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5931
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: > > Hi Dmitry and Paul, > Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
> Thank you, > Jordan > > Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video > Processing | he/him > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Thursday, November 10, 2022 3:34 PM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt > paul.neuhardt@linaro.org > Cc: sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? > > Thanks, > Kim > -----Original Message----- > From: Kim Steiner > Sent: Friday, November 4, 2022 9:49 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul Neuhardt > paul.neuhardt@linaro.org > Cc: sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. > > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Friday, November 4, 2022 8:03 AM > To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner > kim.steiner@sightlineapplications.com > Cc: sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 04/11/2022 17:39, Paul Neuhardt wrote: >> Kim, >> >> I had thought that the latest updates had been posted to your >> repository. My apologies for the misunderstanding. I will ask >> Dmitry to post his updates as soon as possible. > > The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. > >> >> Paul >> >> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >> <kim.steiner@sightlineapplications.com >> mailto:kim.steiner@sightlineapplications.com> wrote: >> >> Hi Paul,____ >> >> __ __ >> >> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >> temp issue may not be fixed. He stated “Thank you for the test. >> I'll work on improving the warming of the CPU/GPU >> then.”____ >> >> __ __ >> >> 2. We still have a very slow boot up time >> (+2minutes).____ >> >> __ __ >> >> 3. I informed Dmitry that the glxgears application only runs for a >> few minutes before stopping.____ >> >> __ __ >> >> __ __ >> >> As of Wednesday (with latest git repository changes), the above >> issues existed and I do not plan on doing any more testing until I >> see new changes or get something new to test.____ >> >> __ __ >> >> I will inform Penguin Solutions that you are close so they can work >> on patches for us to apply to our custom board >> build.____ >> >> __ __ >> >> I would also like to again request a clear set of build instructions >> (changes to .config, compiler, initram…) so that I can build/test >> correctly.____ >> >> __ __ >> >> Thanks,____ >> >> Kim____ >> >> __ __ >> >> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >> mailto:paul.neuhardt@linaro.org> >> *Sent:* Friday, November 4, 2022 7:05 AM >> *To:* sightlineapplications@lists.linaro.org >> mailto:sightlineapplications@lists.linaro.org >> *Subject:* [Sightlineapplications] Project Status and >> Burn Report____ >> >> __ __ >> >> All,____ >> >> __ __ >> >> Dmitry has now delivered what he believes to be the final set of >> updates to Sightline in support of this project. Sightline is in the >> process of testing these deliverables and we expect that the results >> will be at or close to what was expected. If there are still gaps, >> we will of course work to close them.____ >> >> __ __ >> >> As of today, there are still 13.5 hours of Dmitry's time left >> available under the most recent contract extension. This should >> provide adequate time for any consultation needed and any >> updates and/or final tuning necessary. I have attached a brief >> report on that burn to this email. Steve, I will send you a more >> detailed version that you can share inside Sightline as needed. >> ____ >> >> __ __ >> >> Please let me know if you have any questions or concerns. >> ____ >> >> __ __ >> >> While I will continue to be in touch as we close down the project, I >> want to take this opportunity to thank everyone involved for all >> their work. I am confident I speak for all of us at Linaro when I >> say I hope we have the opportunity to work with Sightline >> Applications again in the future.____ >> >> __ __ >> >> Kind regards,____ >> >> Paul____ >> >> -- ____ >> >> Linaro http://www.linaro.org/____ >> >> >> >> *Paul Neuhardt*|/Sr. Program Manager/____ >> >> T: +44 0771 377 8664 >> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >> IRC: pneuhardt____ >> >> __ __ >> >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote:
Hi Dmitry,
In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power:
1.) wait 1 minute with power disconnected. 2.) turn on power. 3.) Usually get one of these:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
Thanks, Kim -----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 8:56 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
The build instructions work for me so I will forward them to Penguin Solutions.
Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
Thanks, Kim
-----Original Message----- From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Tuesday, November 15, 2022 5:43 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I will try these instructions today! Thank you 😊
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, November 15, 2022 5:05 AM To: Jordan Holt jordan.holt@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello, Jordan, Kim,
On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: > > Hi Dmitry and Paul, > Any chance to get these build instructions? We would like to help Penguin to move forward.
I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email.
> Thank you, > Jordan > > Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video > Processing | he/him > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Thursday, November 10, 2022 3:34 PM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul > Neuhardt paul.neuhardt@linaro.org > Cc: sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? > > Thanks, > Kim > -----Original Message----- > From: Kim Steiner > Sent: Friday, November 4, 2022 9:49 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul > Neuhardt paul.neuhardt@linaro.org > Cc: sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and > Burn Report > > Hi Dmitry, > > Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. > > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Friday, November 4, 2022 8:03 AM > To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner > kim.steiner@sightlineapplications.com > Cc: sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and > Burn Report > > Hi Kim, > > On 04/11/2022 17:39, Paul Neuhardt wrote: >> Kim, >> >> I had thought that the latest updates had been posted to your >> repository. My apologies for the misunderstanding. I will ask >> Dmitry to post his updates as soon as possible. > > The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. > >> >> Paul >> >> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >> <kim.steiner@sightlineapplications.com >> mailto:kim.steiner@sightlineapplications.com> wrote: >> >> Hi Paul,____ >> >> __ __ >> >> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >> temp issue may not be fixed. He stated “Thank you for the test. >> I'll work on improving the warming of the CPU/GPU >> then.”____ >> >> __ __ >> >> 2. We still have a very slow boot up time >> (+2minutes).____ >> >> __ __ >> >> 3. I informed Dmitry that the glxgears application only runs for a >> few minutes before stopping.____ >> >> __ __ >> >> __ __ >> >> As of Wednesday (with latest git repository changes), the above >> issues existed and I do not plan on doing any more testing until I >> see new changes or get something new to test.____ >> >> __ __ >> >> I will inform Penguin Solutions that you are close so they can work >> on patches for us to apply to our custom board >> build.____ >> >> __ __ >> >> I would also like to again request a clear set of build instructions >> (changes to .config, compiler, initram…) so that I can build/test >> correctly.____ >> >> __ __ >> >> Thanks,____ >> >> Kim____ >> >> __ __ >> >> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >> mailto:paul.neuhardt@linaro.org> >> *Sent:* Friday, November 4, 2022 7:05 AM >> *To:* sightlineapplications@lists.linaro.org >> mailto:sightlineapplications@lists.linaro.org >> *Subject:* [Sightlineapplications] Project Status and >> Burn Report____ >> >> __ __ >> >> All,____ >> >> __ __ >> >> Dmitry has now delivered what he believes to be the final set of >> updates to Sightline in support of this project. Sightline is in the >> process of testing these deliverables and we expect that the results >> will be at or close to what was expected. If there are still gaps, >> we will of course work to close them.____ >> >> __ __ >> >> As of today, there are still 13.5 hours of Dmitry's time left >> available under the most recent contract extension. This should >> provide adequate time for any consultation needed and any >> updates and/or final tuning necessary. I have attached a brief >> report on that burn to this email. Steve, I will send you a more >> detailed version that you can share inside Sightline as needed. >> ____ >> >> __ __ >> >> Please let me know if you have any questions or concerns. >> ____ >> >> __ __ >> >> While I will continue to be in touch as we close down the project, I >> want to take this opportunity to thank everyone involved for all >> their work. I am confident I speak for all of us at Linaro when I >> say I hope we have the opportunity to work with Sightline >> Applications again in the future.____ >> >> __ __ >> >> Kind regards,____ >> >> Paul____ >> >> -- ____ >> >> Linaro http://www.linaro.org/____ >> >> >> >> *Paul Neuhardt*|/Sr. Program Manager/____ >> >> T: +44 0771 377 8664 >> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >> IRC: pneuhardt____ >> >> __ __ >> >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue?
Yes, please.
I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
Great :-)
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry > Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt jordan.holt@sightlineapplications.com > Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul > Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >> kim.steiner@sightlineapplications.com >> Cc: sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.com >>> mailto:kim.steiner@sightlineapplications.com> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the CPU/GPU >>> then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>> mailto:paul.neuhardt@linaro.org> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.org >>> mailto:sightlineapplications@lists.linaro.org >>> *Subject:* [Sightlineapplications] Project Status and >>> Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
I will hopefully get a chance to test this week.
Did you get my other email with the DM820c picture and build.zip file (from 12/14)? If not, I'll try sending again.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 20, 2022 9:06 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue?
Yes, please.
I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
Great :-)
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry > Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt jordan.holt@sightlineapplications.com > Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul > Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >> kim.steiner@sightlineapplications.com >> Cc: sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.com >>> mailto:kim.steiner@sightlineapplications.com> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the >>> CPU/GPU then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>> mailto:paul.neuhardt@linaro.org> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.org >>> mailto:sightlineapplications@lists.linaro.org >>> *Subject:* [Sightlineapplications] Project Status >>> and Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
On Tue, 20 Dec 2022 at 19:18, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
I will hopefully get a chance to test this week.
Thank you!
Did you get my other email with the DM820c picture and build.zip file (from 12/14)? If not, I'll try sending again.
Ack, I found it now. It slipped through my inbox and I didn't notice the jpeg.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 20, 2022 9:06 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue?
Yes, please.
I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
Great :-)
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. > > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). > >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to Penguin Solutions. >> >> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to help Penguin to move forward. >> >> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>> Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>> temp issue may not be fixed. He stated “Thank you for the test. >>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application only runs for a >>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes), the above >>>> issues existed and I do not plan on doing any more testing until I >>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so they can work >>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of build instructions >>>> (changes to .config, compiler, initram…) so that I can build/test >>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the final set of >>>> updates to Sightline in support of this project. Sightline is in the >>>> process of testing these deliverables and we expect that the results >>>> will be at or close to what was expected. If there are still gaps, >>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's time left >>>> available under the most recent contract extension. This should >>>> provide adequate time for any consultation needed and any >>>> updates and/or final tuning necessary. I have attached a brief >>>> report on that burn to this email. Steve, I will send you a more >>>> detailed version that you can share inside Sightline as needed. >>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or concerns. >>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down the project, I >>>> want to take this opportunity to thank everyone involved for all >>>> their work. I am confident I speak for all of us at Linaro when I >>>> say I hope we have the opportunity to work with Sightline >>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry > Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt jordan.holt@sightlineapplications.com > Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul > Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >> kim.steiner@sightlineapplications.com >> Cc: sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.com >>> mailto:kim.steiner@sightlineapplications.com> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the CPU/GPU >>> then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>> mailto:paul.neuhardt@linaro.org> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.org >>> mailto:sightlineapplications@lists.linaro.org >>> *Subject:* [Sightlineapplications] Project Status and >>> Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?).
We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit?
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry > Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt jordan.holt@sightlineapplications.com > Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul > Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >> kim.steiner@sightlineapplications.com >> Cc: sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.com >>> mailto:kim.steiner@sightlineapplications.com> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the >>> CPU/GPU then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>> mailto:paul.neuhardt@linaro.org> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.org >>> mailto:sightlineapplications@lists.linaro.org >>> *Subject:* [Sightlineapplications] Project Status >>> and Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Steve,
On 21/12/2022 23:52, Steve Olson wrote:
Hi Dmitry,
Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?).
We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit?
Sure:
My shipment address is (note the 'ii' in the name):
Dmitrii Baryshkov Piispanristi 2 A 86 Espoo 02200 Finland
Phone: +358 469526397
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. > > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). > >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to Penguin Solutions. >> >> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to help Penguin to move forward. >> >> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>> Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>> temp issue may not be fixed. He stated “Thank you for the test. >>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application only runs for a >>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes), the above >>>> issues existed and I do not plan on doing any more testing until I >>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so they can work >>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of build instructions >>>> (changes to .config, compiler, initram…) so that I can build/test >>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the final set of >>>> updates to Sightline in support of this project. Sightline is in the >>>> process of testing these deliverables and we expect that the results >>>> will be at or close to what was expected. If there are still gaps, >>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's time left >>>> available under the most recent contract extension. This should >>>> provide adequate time for any consultation needed and any >>>> updates and/or final tuning necessary. I have attached a brief >>>> report on that burn to this email. Steve, I will send you a more >>>> detailed version that you can share inside Sightline as needed. >>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or concerns. >>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down the project, I >>>> want to take this opportunity to thank everyone involved for all >>>> their work. I am confident I speak for all of us at Linaro when I >>>> say I hope we have the opportunity to work with Sightline >>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Steve,
I haven't seen the signed doc back from our COO yet. I'll ask Glen to chase it.
Paul
On Wed, 21 Dec 2022 at 13:52, Steve Olson < steve.olson@sightlineapplications.com> wrote:
Hi Dmitry,
Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?).
We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit?
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt < paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU
temperature issue?
I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner <
kim.steiner@sightlineapplications.com> wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu
cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel:
cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq
issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue
'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using
--pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the
above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW
configuration)
[ 2.799742] arm-smmu 1600000.iommu: stream matching with 15
register groups
[ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2
only)
[ 2.814128] arm-smmu 1600000.iommu: Supported page sizes:
0x63315000
[ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit
IPA
[ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures
happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with
the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu
failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c.
About 50% of the time it stops at around 5seconds and prints this:
[ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered,
assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the
same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm
investigating it now."
On 18th of November I again stated that "Meanwhile I will continue
debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With
the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like
forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
> > What I observe in the serial window is that I see the glxgears
process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this
happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using
'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which
included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I
wait a while to turn on power:
>> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log
Type:
>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm
investigating it now.
> > 2) If the board is in normal conditions, then glxgears can run like
forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
> > 3) I'm working on implementing the additional heating for the low
temperatures using the PMIC regulators (MX and CX power domains).
> >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to
Penguin Solutions.
>> >> Are you still working on the CPU/GPU messaging? It looks like
boot time is quicker (~40s). Did you look into the glxgears application not running for very long?
>> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt <
jordan.holt@sightlineapplications.com> wrote:
>>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to
help Penguin to move forward.
>> >> I have updated the kernel branch with board-specific defconfig.
The build instructions are attached to this email.
>> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>> Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch
for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using?
>>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and
had the issues mentioned to the group. I will wait for new updates to test.
>>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon
as I have any updates from my side, including the heating fine-tuning, etc.
>>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him
that the gpu
>>>> temp issue may not be fixed. He stated “Thank you
for the test.
>>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application
only runs for a
>>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes),
the above
>>>> issues existed and I do not plan on doing any more
testing until I
>>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so
they can work
>>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of
build instructions
>>>> (changes to .config, compiler, initram…) so that I can
build/test
>>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the
final set of
>>>> updates to Sightline in support of this project.
Sightline is in the
>>>> process of testing these deliverables and we expect
that the results
>>>> will be at or close to what was expected. If there are
still gaps,
>>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's
time left
>>>> available under the most recent contract extension.
This should
>>>> provide adequate time for any consultation needed and
any
>>>> updates and/or final tuning necessary. I have attached
a brief
>>>> report on that burn to this email. Steve, I will send
you a more
>>>> detailed version that you can share inside Sightline
as needed.
>>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or
concerns.
>>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down
the project, I
>>>> want to take this opportunity to thank everyone
involved for all
>>>> their work. I am confident I speak for all of us at
Linaro when I
>>>> say I hope we have the opportunity to work with
Sightline
>>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org <mailto:
glen.valante@linaro.org>
>>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
I will pull in the latest changes today and do a bunch of power cycles/reboots and report back.
Unfortunately, I won't be able to do any GPU crash test until next week. I am sick, as Steve pointed out, and don't want to get anyone in the office sick right before the Christmas holiday. I would feel too bad ☹ Next week I will be able to test (as long as I am healthy).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 1:54 PM To: Steve Olson steve.olson@sightlineapplications.com; Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Steve,
On 21/12/2022 23:52, Steve Olson wrote:
Hi Dmitry,
Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?).
We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit?
Sure:
My shipment address is (note the 'ii' in the name):
Dmitrii Baryshkov Piispanristi 2 A 86 Espoo 02200 Finland
Phone: +358 469526397
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Ima g e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/5 9 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. > > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). > >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to Penguin Solutions. >> >> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to help Penguin to move forward. >> >> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>> Video Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>> temp issue may not be fixed. He stated “Thank you for the test. >>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application only runs for a >>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes), the above >>>> issues existed and I do not plan on doing any more testing until I >>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so they can work >>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of build instructions >>>> (changes to .config, compiler, initram…) so that I can build/test >>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the final set of >>>> updates to Sightline in support of this project. Sightline is in the >>>> process of testing these deliverables and we expect that the results >>>> will be at or close to what was expected. If there are still gaps, >>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's time left >>>> available under the most recent contract extension. This should >>>> provide adequate time for any consultation needed and any >>>> updates and/or final tuning necessary. I have attached a brief >>>> report on that burn to this email. Steve, I will send you a more >>>> detailed version that you can share inside Sightline as needed. >>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or concerns. >>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down the project, I >>>> want to take this opportunity to thank everyone involved for all >>>> their work. I am confident I speak for all of us at Linaro when I >>>> say I hope we have the opportunity to work with Sightline >>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hello Steve;
Please find attached, a fully executed copy of the Proposal. If you need anything else, I will be here over most of the holidays.
Thanks;
-g
On 12/21/2022 6:11 PM, Paul Neuhardt wrote:
Steve,
I haven't seen the signed doc back from our COO yet. I'll ask Glen to chase it.
Paul
On Wed, 21 Dec 2022 at 13:52, Steve Olson steve.olson@sightlineapplications.com wrote:
Hi Dmitry, Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?). We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit? Thanks, Steve Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com <http://www.sightlineapplications.com> -----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner <kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report Hi Kim, On 20/12/2022 19:01, Kim Steiner wrote: > Hi Dmitry, > > With these cpufreq changes to the branch, can I test the original GPU temperature issue? > I don't think I mentioned it, but boot time seems faster now with the > cpufreq patch you last sent 😊 I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore. BTW: any progress on shipping your hardware? > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > Sent: Monday, December 19, 2022 4:45 PM > To: Kim Steiner <kim.steiner@sightlineapplications.com> > Cc: Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt > <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On Sat, 3 Dec 2022 at 00:19, Kim Steiner <kim.steiner@sightlineapplications.com> wrote: >> >> Hi Dmitry, >> >> It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: >> cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max >> 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz >> --max 1000Mhz > > I have updated the release branch with the patches that fix the cpufreq issue. > > Using this kernel and these commands I can set the required frequencies: > > # cpufreq-info | grep current > current policy: frequency should be within 1.04 GHz and 1.04 GHz. > current CPU frequency is 1.04 GHz (asserted by call to hardware). > current policy: frequency should be within 1.04 GHz and 1.04 GHz. > current CPU frequency is 1.04 GHz (asserted by call to hardware). > current policy: frequency should be within 1.04 GHz and 1.04 GHz. > current CPU frequency is 1.04 GHz (asserted by call to hardware). > current policy: frequency should be within 1.04 GHz and 1.04 GHz. > current CPU frequency is 1.04 GHz (asserted by call to hardware). > >> >> but they do not work in the 5.15 branch. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, December 2, 2022 12:38 PM >> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt >> <jordan.holt@sightlineapplications.com> >> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors). >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >> Sent: Wednesday, November 30, 2022 12:22 PM >> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan Holt >> <jordan.holt@sightlineapplications.com> >> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> On 28/11/2022 22:19, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> With this patch, I built per your instructions. I got this error >>> when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 >>> [190] panic (caller 0x91637134): ASSERT FAILED at >>> (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) >>> [200] HALT: reboot into dload mo >>> >>> So I change the --pagesize to 4096 and built the image again and it >>> worked. It looks like the db820c should use 4096 per this page: >>> https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag >>> e >> >> Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here. >> >> If 4096 works for you, let's use it. >> >>> >>> I cycled power 15 or so times and only had one failed boot with the above patch: >>> >>> [ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) >>> [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups >>> [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) >>> [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 >>> [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA >>> [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84) >> >> Interesting. I'll run additional tests on my side. >> >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> S - IMAGE_VARIANT_STRING=M8996LAB >>> S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>> S - Boot Interface: UFS >>> S - Secure Boot: Off >>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = >>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ >>> 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = >>> 0x0000000000000000 >>> >>> I'm not sure if this boot failure is the same as the 4.14 boot >>> failure or not: >>> https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 >>> 31 >> >> No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered. >> >>> >>> Also, would it be possible for me to get your boot.img to compare with the one I built? >> >> I have uploaded my image to: [1] >> >> [1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs >> >>> >>> Thanks, >>> >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>> Sent: Thursday, November 24, 2022 11:16 AM >>> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan Holt >>> <jordan.holt@sightlineapplications.com> >>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Kim, >>> >>> On 23/11/2022 23:57, Kim Steiner wrote: >>>> Got it, thanks! >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>>> Sent: Wednesday, November 23, 2022 12:04 PM >>>> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan >>>> Holt <jordan.holt@sightlineapplications.com> >>>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>>> sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Kim, >>>> >>>> On 23/11/2022 01:52, Kim Steiner wrote: >>>>> Hi Dmitry, >>>>> >>>>> I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would. >>>> >>>> This sounds great! >>>> >>>>> >>>>> I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: >>>>> [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 >>>>> >>>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>>> >>>>> Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me. >>>> >>>> Probably there is some misunderstanding. On 17th of November i wrote: >>>> "1) I was able to reproduce the failure during the cold boot. I'm investigating it now." >>>> >>>> On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. " >>> >>> It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch. >>> >>>> >>>>> >>>>> Thanks, >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>>>> Sent: Friday, November 18, 2022 12:42 PM >>>>> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan >>>>> Holt <jordan.holt@sightlineapplications.com> >>>>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>>>> Report >>>>> >>>>> Hi Kim, >>>>> >>>>> First, I have updated the release branch. The changes included are: >>>>> >>>>> - fix warming up code in the thermal subsystem to behave more >>>>> aggressively >>>>> - add more warming up sources to the CPU and GPU devices >>>>> - add separate driver to use MX and CX power rails to warm up the >>>>> GPU >>>>> >>>>> Could you please give this release a test? >>>>> Meanwhile I will continue debugging the 'boot up reboot' issue. >>>>> >>>>> On 17/11/2022 15:35, Kim Steiner wrote: >>>>>> Hi Dmitry, >>>>>> In response to: >>>>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>>>> >>>>>> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? >>>>> >>>>> Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? >>>>> >>>>> If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' >>>>> >>>>> I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. >>>>> >>>>>> >>>>>> Thanks, >>>>>> Kim >>>>>> >>>>>> -----Original Message----- >>>>>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>>>>> Sent: Wednesday, November 16, 2022 2:15 PM >>>>>> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan >>>>>> Holt <jordan.holt@sightlineapplications.com> >>>>>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>>>>> sightlineapplications@lists.linaro.org >>>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>>> Report >>>>>> >>>>>> Hi Kim, >>>>>> >>>>>> On 15/11/2022 20:15, Kim Steiner wrote: >>>>>>> Hi Dmitry, >>>>>>> >>>>>>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>>>>>> >>>>>>> 1.) wait 1 minute with power disconnected. >>>>>>> 2.) turn on power. >>>>>>> 3.) Usually get one of these: >>>>>>> >>>>>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>>>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>>>>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>>>>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>>>>>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>>>>>> S - Boot Interface: UFS >>>>>>> S - Secure Boot: Off >>>>>>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>>>>>> 0x000760f4 = >>>>>>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >>>>>> >>>>>> I did a lot of testing. Short summary: >>>>>> >>>>>> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >>>>>> >>>>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>>>> >>>>>> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Kim >>>>>>> -----Original Message----- >>>>>>> From: Kim Steiner <kim.steiner@sightlineapplications.com> >>>>>>> Sent: Tuesday, November 15, 2022 8:56 AM >>>>>>> To: Kim Steiner <kim.steiner@sightlineapplications.com>; Dmitry >>>>>>> Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt >>>>>>> <jordan.holt@sightlineapplications.com> >>>>>>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >>>>>>> Report >>>>>>> >>>>>>> Hi Dmitry, >>>>>>> >>>>>>> The build instructions work for me so I will forward them to Penguin Solutions. >>>>>>> >>>>>>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>>>>>> >>>>>>> Thanks, >>>>>>> Kim >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Kim Steiner <kim.steiner@sightlineapplications.com> >>>>>>> Sent: Tuesday, November 15, 2022 5:43 AM >>>>>>> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt >>>>>>> <jordan.holt@sightlineapplications.com> >>>>>>> Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>>>> Report >>>>>>> >>>>>>> Hi Dmitry, >>>>>>> >>>>>>> I will try these instructions today! Thank you 😊 >>>>>>> >>>>>>> Kim >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>>>>>> Sent: Tuesday, November 15, 2022 5:05 AM >>>>>>> To: Jordan Holt <jordan.holt@sightlineapplications.com> >>>>>>> Cc: Kim Steiner <kim.steiner@sightlineapplications.com>; Paul >>>>>>> Neuhardt <paul.neuhardt@linaro.org>; >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>>>>>> Report >>>>>>> >>>>>>> Hello, Jordan, Kim, >>>>>>> >>>>>>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt <jordan.holt@sightlineapplications.com> wrote: >>>>>>>> >>>>>>>> Hi Dmitry and Paul, >>>>>>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>>>>>> >>>>>>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>>>>>> >>>>>>>> Thank you, >>>>>>>> Jordan >>>>>>>> >>>>>>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>>>>>>> Processing | he/him >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Kim Steiner <kim.steiner@sightlineapplications.com> >>>>>>>> Sent: Thursday, November 10, 2022 3:34 PM >>>>>>>> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Paul >>>>>>>> Neuhardt <paul.neuhardt@linaro.org> >>>>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>>>>> Report >>>>>>>> >>>>>>>> Hi Dmitry, >>>>>>>> >>>>>>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Kim >>>>>>>> -----Original Message----- >>>>>>>> From: Kim Steiner >>>>>>>> Sent: Friday, November 4, 2022 9:49 AM >>>>>>>> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Paul >>>>>>>> Neuhardt <paul.neuhardt@linaro.org> >>>>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>>>>> Burn Report >>>>>>>> >>>>>>>> Hi Dmitry, >>>>>>>> >>>>>>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Kim >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> >>>>>>>> Sent: Friday, November 4, 2022 8:03 AM >>>>>>>> To: Paul Neuhardt <paul.neuhardt@linaro.org>; Kim Steiner >>>>>>>> <kim.steiner@sightlineapplications.com> >>>>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>>>>> Burn Report >>>>>>>> >>>>>>>> Hi Kim, >>>>>>>> >>>>>>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>>>>>> Kim, >>>>>>>>> >>>>>>>>> I had thought that the latest updates had been posted to your >>>>>>>>> repository. My apologies for the misunderstanding. I will ask >>>>>>>>> Dmitry to post his updates as soon as possible. >>>>>>>> >>>>>>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>>>>>> >>>>>>>>> >>>>>>>>> Paul >>>>>>>>> >>>>>>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>>>>>> <kim.steiner@sightlineapplications.com >>>>>>>>> <mailto:kim.steiner@sightlineapplications.com>> wrote: >>>>>>>>> >>>>>>>>> Hi Paul,____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>>>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>>>>>> I'll work on improving the warming of the >>>>>>>>> CPU/GPU then.”____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> 2. We still have a very slow boot up time >>>>>>>>> (+2minutes).____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>>>>>> few minutes before stopping.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> As of Wednesday (with latest git repository changes), the above >>>>>>>>> issues existed and I do not plan on doing any more testing until I >>>>>>>>> see new changes or get something new to test.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> I will inform Penguin Solutions that you are close so they can work >>>>>>>>> on patches for us to apply to our custom board >>>>>>>>> build.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> I would also like to again request a clear set of build instructions >>>>>>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>>>>>> correctly.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> Thanks,____ >>>>>>>>> >>>>>>>>> Kim____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>>>>>> <mailto:paul.neuhardt@linaro.org>> >>>>>>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>>>>>> *To:* sightlineapplications@lists.linaro.org >>>>>>>>> <mailto:sightlineapplications@lists.linaro.org> >>>>>>>>> *Subject:* [Sightlineapplications] Project Status >>>>>>>>> and Burn Report____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> All,____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> Dmitry has now delivered what he believes to be the final set of >>>>>>>>> updates to Sightline in support of this project. Sightline is in the >>>>>>>>> process of testing these deliverables and we expect that the results >>>>>>>>> will be at or close to what was expected. If there are still gaps, >>>>>>>>> we will of course work to close them.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>>>>>> available under the most recent contract extension. This should >>>>>>>>> provide adequate time for any consultation needed and any >>>>>>>>> updates and/or final tuning necessary. I have attached a brief >>>>>>>>> report on that burn to this email. Steve, I will send you a more >>>>>>>>> detailed version that you can share inside Sightline as needed. >>>>>>>>> ____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> Please let me know if you have any questions or concerns. >>>>>>>>> ____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> While I will continue to be in touch as we close down the project, I >>>>>>>>> want to take this opportunity to thank everyone involved for all >>>>>>>>> their work. I am confident I speak for all of us at Linaro when I >>>>>>>>> say I hope we have the opportunity to work with Sightline >>>>>>>>> Applications again in the future.____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> Kind regards,____ >>>>>>>>> >>>>>>>>> Paul____ >>>>>>>>> >>>>>>>>> -- ____ >>>>>>>>> >>>>>>>>> Linaro <http://www.linaro.org/>____ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>>>>>> >>>>>>>>> T: +44 0771 377 8664 >>>>>>>>> paul.neuhardt@linaro.org <mailto:glen.valante@linaro.org> >>>>>>>>> IRC: pneuhardt____ >>>>>>>>> >>>>>>>>> __ __ >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Sightlineapplications mailing list -- >>>>>>>>> sightlineapplications@lists.linaro.org >>>>>>>>> To unsubscribe send an email to >>>>>>>>> sightlineapplications-leave@lists.linaro.org >>>>>>>> >>>>>>>> -- >>>>>>>> With best wishes >>>>>>>> Dmitry >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Sightlineapplications mailing list -- >>>>>>>> sightlineapplications@lists.linaro.org >>>>>>>> To unsubscribe send an email to >>>>>>>> sightlineapplications-leave@lists.linaro.org >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> With best wishes >>>>>>> Dmitry >>>>>>> _______________________________________________ >>>>>>> Sightlineapplications mailing list -- >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> To unsubscribe send an email to >>>>>>> sightlineapplications-leave@lists.linaro.org >>>>>> >>>>>> -- >>>>>> With best wishes >>>>>> Dmitry >>>>>> >>>>>> _______________________________________________ >>>>>> Sightlineapplications mailing list -- >>>>>> sightlineapplications@lists.linaro.org >>>>>> To unsubscribe send an email to >>>>>> sightlineapplications-leave@lists.linaro.org >>>>> >>>>> -- >>>>> With best wishes >>>>> Dmitry >>>>> >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>> >>> -- >>> With best wishes >>> Dmitry >> >> -- >> With best wishes >> Dmitry > > > > -- > With best wishes > Dmitry -- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org-- Linaro http://www.linaro.org/ Paul Neuhardt | /Sr. Program Manager/ T: +44 0771 377 8664 paul.neuhardt@linaro.org mailto:glen.valante@linaro.org IRC: pneuhardt
Thanks, Glen.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com/
From: Glen Valante glen.valante@linaro.org Sent: Thursday, December 22, 2022 6:56 AM To: Paul Neuhardt paul.neuhardt@linaro.org; Steve Olson steve.olson@sightlineapplications.com Cc: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com; Kim Steiner kim.steiner@sightlineapplications.com; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hello Steve;
Please find attached, a fully executed copy of the Proposal. If you need anything else, I will be here over most of the holidays.
Thanks;
-g
On 12/21/2022 6:11 PM, Paul Neuhardt wrote: Steve,
I haven't seen the signed doc back from our COO yet. I'll ask Glen to chase it.
Paul
On Wed, 21 Dec 2022 at 13:52, Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> wrote: Hi Dmitry,
Kim's out sick today, so probably won't see your not until tomorrow. I was thinking I'd wait until I got back the completed contract from Linaro, but I haven't seen it yet (Paul, did I miss it?).
We don't really need to hold things up on that however. Dmitry, can you give me a shipping address where we should set the kit?
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Dmitry > Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Jordan Holt > <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> > Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; > sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Jordan Holt > <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> > Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; > sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> > Cc: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Paul > Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; > sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Paul >> Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org> >> Cc: sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Paul >> Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org> >> Cc: sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; Kim Steiner >> <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> >> Cc: sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com >>> <mailto:kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the >>> CPU/GPU then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org >>> <mailto:paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >>> <mailto:sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org> >>> *Subject:* [Sightlineapplications] Project Status >>> and Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org <mailto:glen.valante@linaro.orgmailto:glen.valante@linaro.org> >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org -- [Image removed by sender. Linaro]http://www.linaro.org/ Paul Neuhardt | Sr. Program Manager T: +44 0771 377 8664 paul.neuhardt@linaro.orgmailto:glen.valante@linaro.org IRC: pneuhardt
-- [Image removed by sender. Linaro]http://www.linaro.org/ Glen Valante | Sr. Technical Program Manager T: +1.508.517.3461tel:1617-320-5000 glen.valante@linaro.orgmailto:glen.valante@linaro.org | Skype: gvalantecallto:gvalante
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote:
Hi Dmitry, In response to: 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 16, 2022 2:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 15/11/2022 20:15, Kim Steiner wrote: > Hi Dmitry, > > In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: > > 1.) wait 1 minute with power disconnected. > 2.) turn on power. > 3.) Usually get one of these: > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000
I did a lot of testing. Short summary:
I was able to reproduce the failure during the cold boot. I'm investigating it now.
If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled).
I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains).
> > Thanks, > Kim > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 8:56 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry > Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: RE: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > The build instructions work for me so I will forward them to Penguin Solutions. > > Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? > > Thanks, > Kim > > -----Original Message----- > From: Kim Steiner kim.steiner@sightlineapplications.com > Sent: Tuesday, November 15, 2022 5:43 AM > To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt > jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Dmitry, > > I will try these instructions today! Thank you 😊 > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Tuesday, November 15, 2022 5:05 AM > To: Jordan Holt jordan.holt@sightlineapplications.com > Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul > Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hello, Jordan, Kim, > > On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >> >> Hi Dmitry and Paul, >> Any chance to get these build instructions? We would like to help Penguin to move forward. > > I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. > >> Thank you, >> Jordan >> >> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >> Processing | he/him >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Thursday, November 10, 2022 3:34 PM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner >> Sent: Friday, November 4, 2022 9:49 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >> Neuhardt paul.neuhardt@linaro.org >> Cc: sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Dmitry, >> >> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 4, 2022 8:03 AM >> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >> kim.steiner@sightlineapplications.com >> Cc: sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 04/11/2022 17:39, Paul Neuhardt wrote: >>> Kim, >>> >>> I had thought that the latest updates had been posted to your >>> repository. My apologies for the misunderstanding. I will ask >>> Dmitry to post his updates as soon as possible. >> >> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >> >>> >>> Paul >>> >>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>> <kim.steiner@sightlineapplications.com >>> mailto:kim.steiner@sightlineapplications.com> wrote: >>> >>> Hi Paul,____ >>> >>> __ __ >>> >>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>> temp issue may not be fixed. He stated “Thank you for the test. >>> I'll work on improving the warming of the >>> CPU/GPU then.”____ >>> >>> __ __ >>> >>> 2. We still have a very slow boot up time >>> (+2minutes).____ >>> >>> __ __ >>> >>> 3. I informed Dmitry that the glxgears application only runs for a >>> few minutes before stopping.____ >>> >>> __ __ >>> >>> __ __ >>> >>> As of Wednesday (with latest git repository changes), the above >>> issues existed and I do not plan on doing any more testing until I >>> see new changes or get something new to test.____ >>> >>> __ __ >>> >>> I will inform Penguin Solutions that you are close so they can work >>> on patches for us to apply to our custom board >>> build.____ >>> >>> __ __ >>> >>> I would also like to again request a clear set of build instructions >>> (changes to .config, compiler, initram…) so that I can build/test >>> correctly.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Kim____ >>> >>> __ __ >>> >>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>> mailto:paul.neuhardt@linaro.org> >>> *Sent:* Friday, November 4, 2022 7:05 AM >>> *To:* sightlineapplications@lists.linaro.org >>> mailto:sightlineapplications@lists.linaro.org >>> *Subject:* [Sightlineapplications] Project Status >>> and Burn Report____ >>> >>> __ __ >>> >>> All,____ >>> >>> __ __ >>> >>> Dmitry has now delivered what he believes to be the final set of >>> updates to Sightline in support of this project. Sightline is in the >>> process of testing these deliverables and we expect that the results >>> will be at or close to what was expected. If there are still gaps, >>> we will of course work to close them.____ >>> >>> __ __ >>> >>> As of today, there are still 13.5 hours of Dmitry's time left >>> available under the most recent contract extension. This should >>> provide adequate time for any consultation needed and any >>> updates and/or final tuning necessary. I have attached a brief >>> report on that burn to this email. Steve, I will send you a more >>> detailed version that you can share inside Sightline as needed. >>> ____ >>> >>> __ __ >>> >>> Please let me know if you have any questions or concerns. >>> ____ >>> >>> __ __ >>> >>> While I will continue to be in touch as we close down the project, I >>> want to take this opportunity to thank everyone involved for all >>> their work. I am confident I speak for all of us at Linaro when I >>> say I hope we have the opportunity to work with Sightline >>> Applications again in the future.____ >>> >>> __ __ >>> >>> Kind regards,____ >>> >>> Paul____ >>> >>> -- ____ >>> >>> Linaro http://www.linaro.org/____ >>> >>> >>> >>> *Paul Neuhardt*|/Sr. Program Manager/____ >>> >>> T: +44 0771 377 8664 >>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>> IRC: pneuhardt____ >>> >>> __ __ >>> >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > > > -- > With best wishes > Dmitry > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. > > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). > >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to Penguin Solutions. >> >> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to help Penguin to move forward. >> >> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>> Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>> temp issue may not be fixed. He stated “Thank you for the test. >>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application only runs for a >>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes), the above >>>> issues existed and I do not plan on doing any more testing until I >>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so they can work >>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of build instructions >>>> (changes to .config, compiler, initram…) so that I can build/test >>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the final set of >>>> updates to Sightline in support of this project. Sightline is in the >>>> process of testing these deliverables and we expect that the results >>>> will be at or close to what was expected. If there are still gaps, >>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's time left >>>> available under the most recent contract extension. This should >>>> provide adequate time for any consultation needed and any >>>> updates and/or final tuning necessary. I have attached a brief >>>> report on that burn to this email. Steve, I will send you a more >>>> detailed version that you can share inside Sightline as needed. >>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or concerns. >>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down the project, I >>>> want to take this opportunity to thank everyone involved for all >>>> their work. I am confident I speak for all of us at Linaro when I >>>> say I hope we have the opportunity to work with Sightline >>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote:
Hi Dmitry,
I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, November 18, 2022 12:42 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
First, I have updated the release branch. The changes included are:
- fix warming up code in the thermal subsystem to behave more aggressively
- add more warming up sources to the CPU and GPU devices
- add separate driver to use MX and CX power rails to warm up the
GPU
Could you please give this release a test? Meanwhile I will continue debugging the 'boot up reboot' issue.
On 17/11/2022 15:35, Kim Steiner wrote: > Hi Dmitry, > In response to: > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you?
Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case?
If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears'
I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 16, 2022 2:15 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 15/11/2022 20:15, Kim Steiner wrote: >> Hi Dmitry, >> >> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >> >> 1.) wait 1 minute with power disconnected. >> 2.) turn on power. >> 3.) Usually get one of these: >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> S - IMAGE_VARIANT_STRING=M8996LAB S - >> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >> S - Boot Interface: UFS >> S - Secure Boot: Off >> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >> 0x000760f4 = >> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 > > I did a lot of testing. Short summary: > > 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. > > 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). > > 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). > >> >> Thanks, >> Kim >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 8:56 AM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> The build instructions work for me so I will forward them to Penguin Solutions. >> >> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Kim Steiner kim.steiner@sightlineapplications.com >> Sent: Tuesday, November 15, 2022 5:43 AM >> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >> jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Dmitry, >> >> I will try these instructions today! Thank you 😊 >> >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Tuesday, November 15, 2022 5:05 AM >> To: Jordan Holt jordan.holt@sightlineapplications.com >> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >> Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hello, Jordan, Kim, >> >> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>> >>> Hi Dmitry and Paul, >>> Any chance to get these build instructions? We would like to help Penguin to move forward. >> >> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >> >>> Thank you, >>> Jordan >>> >>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>> Processing | he/him >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Thursday, November 10, 2022 3:34 PM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner >>> Sent: Friday, November 4, 2022 9:49 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>> Neuhardt paul.neuhardt@linaro.org >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 4, 2022 8:03 AM >>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>> kim.steiner@sightlineapplications.com >>> Cc: sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>> Kim, >>>> >>>> I had thought that the latest updates had been posted to your >>>> repository. My apologies for the misunderstanding. I will ask >>>> Dmitry to post his updates as soon as possible. >>> >>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>> >>>> >>>> Paul >>>> >>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>> <kim.steiner@sightlineapplications.com >>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>> >>>> Hi Paul,____ >>>> >>>> __ __ >>>> >>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>> temp issue may not be fixed. He stated “Thank you for the test. >>>> I'll work on improving the warming of the >>>> CPU/GPU then.”____ >>>> >>>> __ __ >>>> >>>> 2. We still have a very slow boot up time >>>> (+2minutes).____ >>>> >>>> __ __ >>>> >>>> 3. I informed Dmitry that the glxgears application only runs for a >>>> few minutes before stopping.____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> As of Wednesday (with latest git repository changes), the above >>>> issues existed and I do not plan on doing any more testing until I >>>> see new changes or get something new to test.____ >>>> >>>> __ __ >>>> >>>> I will inform Penguin Solutions that you are close so they can work >>>> on patches for us to apply to our custom board >>>> build.____ >>>> >>>> __ __ >>>> >>>> I would also like to again request a clear set of build instructions >>>> (changes to .config, compiler, initram…) so that I can build/test >>>> correctly.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Kim____ >>>> >>>> __ __ >>>> >>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>> mailto:paul.neuhardt@linaro.org> >>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>> *To:* sightlineapplications@lists.linaro.org >>>> mailto:sightlineapplications@lists.linaro.org >>>> *Subject:* [Sightlineapplications] Project Status >>>> and Burn Report____ >>>> >>>> __ __ >>>> >>>> All,____ >>>> >>>> __ __ >>>> >>>> Dmitry has now delivered what he believes to be the final set of >>>> updates to Sightline in support of this project. Sightline is in the >>>> process of testing these deliverables and we expect that the results >>>> will be at or close to what was expected. If there are still gaps, >>>> we will of course work to close them.____ >>>> >>>> __ __ >>>> >>>> As of today, there are still 13.5 hours of Dmitry's time left >>>> available under the most recent contract extension. This should >>>> provide adequate time for any consultation needed and any >>>> updates and/or final tuning necessary. I have attached a brief >>>> report on that burn to this email. Steve, I will send you a more >>>> detailed version that you can share inside Sightline as needed. >>>> ____ >>>> >>>> __ __ >>>> >>>> Please let me know if you have any questions or concerns. >>>> ____ >>>> >>>> __ __ >>>> >>>> While I will continue to be in touch as we close down the project, I >>>> want to take this opportunity to thank everyone involved for all >>>> their work. I am confident I speak for all of us at Linaro when I >>>> say I hope we have the opportunity to work with Sightline >>>> Applications again in the future.____ >>>> >>>> __ __ >>>> >>>> Kind regards,____ >>>> >>>> Paul____ >>>> >>>> -- ____ >>>> >>>> Linaro http://www.linaro.org/____ >>>> >>>> >>>> >>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>> >>>> T: +44 0771 377 8664 >>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>> IRC: pneuhardt____ >>>> >>>> __ __ >>>> >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> >> >> -- >> With best wishes >> Dmitry >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry > > _______________________________________________ > Sightlineapplications mailing list -- > sightlineapplications@lists.linaro.org > To unsubscribe send an email to > sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
I hope you feel better now!
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance?
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Imag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote: > Hi Dmitry, > > I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
> > I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: > [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > > Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Friday, November 18, 2022 12:42 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > First, I have updated the release branch. The changes included are: > > - fix warming up code in the thermal subsystem to behave more > aggressively > - add more warming up sources to the CPU and GPU devices > - add separate driver to use MX and CX power rails to warm up the > GPU > > Could you please give this release a test? > Meanwhile I will continue debugging the 'boot up reboot' issue. > > On 17/11/2022 15:35, Kim Steiner wrote: >> Hi Dmitry, >> In response to: >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? > > Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? > > If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' > > I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. > >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Wednesday, November 16, 2022 2:15 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> On 15/11/2022 20:15, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>> >>> 1.) wait 1 minute with power disconnected. >>> 2.) turn on power. >>> 3.) Usually get one of these: >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>> S - Boot Interface: UFS >>> S - Secure Boot: Off >>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>> 0x000760f4 = >>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >> >> I did a lot of testing. Short summary: >> >> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >> >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >> >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 8:56 AM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; Dmitry >>> Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>> jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> The build instructions work for me so I will forward them to Penguin Solutions. >>> >>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 5:43 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>> jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I will try these instructions today! Thank you 😊 >>> >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Tuesday, November 15, 2022 5:05 AM >>> To: Jordan Holt jordan.holt@sightlineapplications.com >>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>> Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hello, Jordan, Kim, >>> >>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>> >>>> Hi Dmitry and Paul, >>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>> >>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>> >>>> Thank you, >>>> Jordan >>>> >>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video >>>> Processing | he/him >>>> >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Thursday, November 10, 2022 3:34 PM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Dmitry, >>>> >>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>> >>>> Thanks, >>>> Kim >>>> -----Original Message----- >>>> From: Kim Steiner >>>> Sent: Friday, November 4, 2022 9:49 AM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Dmitry, >>>> >>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Friday, November 4, 2022 8:03 AM >>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>> kim.steiner@sightlineapplications.com >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Kim, >>>> >>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>> Kim, >>>>> >>>>> I had thought that the latest updates had been posted to your >>>>> repository. My apologies for the misunderstanding. I will ask >>>>> Dmitry to post his updates as soon as possible. >>>> >>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>> >>>>> >>>>> Paul >>>>> >>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>> <kim.steiner@sightlineapplications.com >>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>> >>>>> Hi Paul,____ >>>>> >>>>> __ __ >>>>> >>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>> I'll work on improving the warming of the >>>>> CPU/GPU then.”____ >>>>> >>>>> __ __ >>>>> >>>>> 2. We still have a very slow boot up time >>>>> (+2minutes).____ >>>>> >>>>> __ __ >>>>> >>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>> few minutes before stopping.____ >>>>> >>>>> __ __ >>>>> >>>>> __ __ >>>>> >>>>> As of Wednesday (with latest git repository changes), the above >>>>> issues existed and I do not plan on doing any more testing until I >>>>> see new changes or get something new to test.____ >>>>> >>>>> __ __ >>>>> >>>>> I will inform Penguin Solutions that you are close so they can work >>>>> on patches for us to apply to our custom board >>>>> build.____ >>>>> >>>>> __ __ >>>>> >>>>> I would also like to again request a clear set of build instructions >>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>> correctly.____ >>>>> >>>>> __ __ >>>>> >>>>> Thanks,____ >>>>> >>>>> Kim____ >>>>> >>>>> __ __ >>>>> >>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>> mailto:paul.neuhardt@linaro.org> >>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>> *To:* sightlineapplications@lists.linaro.org >>>>> mailto:sightlineapplications@lists.linaro.org >>>>> *Subject:* [Sightlineapplications] Project Status >>>>> and Burn Report____ >>>>> >>>>> __ __ >>>>> >>>>> All,____ >>>>> >>>>> __ __ >>>>> >>>>> Dmitry has now delivered what he believes to be the final set of >>>>> updates to Sightline in support of this project. Sightline is in the >>>>> process of testing these deliverables and we expect that the results >>>>> will be at or close to what was expected. If there are still gaps, >>>>> we will of course work to close them.____ >>>>> >>>>> __ __ >>>>> >>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>> available under the most recent contract extension. This should >>>>> provide adequate time for any consultation needed and any >>>>> updates and/or final tuning necessary. I have attached a brief >>>>> report on that burn to this email. Steve, I will send you a more >>>>> detailed version that you can share inside Sightline as needed. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> Please let me know if you have any questions or concerns. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> While I will continue to be in touch as we close down the project, I >>>>> want to take this opportunity to thank everyone involved for all >>>>> their work. I am confident I speak for all of us at Linaro when I >>>>> say I hope we have the opportunity to work with Sightline >>>>> Applications again in the future.____ >>>>> >>>>> __ __ >>>>> >>>>> Kind regards,____ >>>>> >>>>> Paul____ >>>>> >>>>> -- ____ >>>>> >>>>> Linaro http://www.linaro.org/____ >>>>> >>>>> >>>>> >>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>> >>>>> T: +44 0771 377 8664 >>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>> IRC: pneuhardt____ >>>>> >>>>> __ __ >>>>> >>>>> >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> >>> >>> -- >>> With best wishes >>> Dmitry >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry >
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Im ag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/ 59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote: > Hi Dmitry, > > I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
> > I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: > [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > > Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Friday, November 18, 2022 12:42 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > First, I have updated the release branch. The changes included are: > > - fix warming up code in the thermal subsystem to behave more > aggressively > - add more warming up sources to the CPU and GPU devices > - add separate driver to use MX and CX power rails to warm up > the GPU > > Could you please give this release a test? > Meanwhile I will continue debugging the 'boot up reboot' issue. > > On 17/11/2022 15:35, Kim Steiner wrote: >> Hi Dmitry, >> In response to: >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? > > Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? > > If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' > > I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. > >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Wednesday, November 16, 2022 2:15 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> On 15/11/2022 20:15, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>> >>> 1.) wait 1 minute with power disconnected. >>> 2.) turn on power. >>> 3.) Usually get one of these: >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>> S - Boot Interface: UFS >>> S - Secure Boot: Off >>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>> 0x000760f4 = >>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >> >> I did a lot of testing. Short summary: >> >> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >> >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >> >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 8:56 AM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>> jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> The build instructions work for me so I will forward them to Penguin Solutions. >>> >>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 5:43 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>> Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I will try these instructions today! Thank you 😊 >>> >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Tuesday, November 15, 2022 5:05 AM >>> To: Jordan Holt jordan.holt@sightlineapplications.com >>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>> Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hello, Jordan, Kim, >>> >>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>> >>>> Hi Dmitry and Paul, >>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>> >>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>> >>>> Thank you, >>>> Jordan >>>> >>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>> Video Processing | he/him >>>> >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Thursday, November 10, 2022 3:34 PM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Dmitry, >>>> >>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>> >>>> Thanks, >>>> Kim >>>> -----Original Message----- >>>> From: Kim Steiner >>>> Sent: Friday, November 4, 2022 9:49 AM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Dmitry, >>>> >>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Friday, November 4, 2022 8:03 AM >>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>> kim.steiner@sightlineapplications.com >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Kim, >>>> >>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>> Kim, >>>>> >>>>> I had thought that the latest updates had been posted to >>>>> your repository. My apologies for the misunderstanding. I >>>>> will ask Dmitry to post his updates as soon as possible. >>>> >>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>> >>>>> >>>>> Paul >>>>> >>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>> <kim.steiner@sightlineapplications.com >>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>> >>>>> Hi Paul,____ >>>>> >>>>> __ __ >>>>> >>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>> I'll work on improving the warming of the >>>>> CPU/GPU then.”____ >>>>> >>>>> __ __ >>>>> >>>>> 2. We still have a very slow boot up time >>>>> (+2minutes).____ >>>>> >>>>> __ __ >>>>> >>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>> few minutes before stopping.____ >>>>> >>>>> __ __ >>>>> >>>>> __ __ >>>>> >>>>> As of Wednesday (with latest git repository changes), the above >>>>> issues existed and I do not plan on doing any more testing until I >>>>> see new changes or get something new to >>>>> test.____ >>>>> >>>>> __ __ >>>>> >>>>> I will inform Penguin Solutions that you are close so they can work >>>>> on patches for us to apply to our custom board >>>>> build.____ >>>>> >>>>> __ __ >>>>> >>>>> I would also like to again request a clear set of build instructions >>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>> correctly.____ >>>>> >>>>> __ __ >>>>> >>>>> Thanks,____ >>>>> >>>>> Kim____ >>>>> >>>>> __ __ >>>>> >>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>> mailto:paul.neuhardt@linaro.org> >>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>> *To:* sightlineapplications@lists.linaro.org >>>>> mailto:sightlineapplications@lists.linaro.org >>>>> *Subject:* [Sightlineapplications] Project >>>>> Status and Burn Report____ >>>>> >>>>> __ __ >>>>> >>>>> All,____ >>>>> >>>>> __ __ >>>>> >>>>> Dmitry has now delivered what he believes to be the final set of >>>>> updates to Sightline in support of this project. Sightline is in the >>>>> process of testing these deliverables and we expect that the results >>>>> will be at or close to what was expected. If there are still gaps, >>>>> we will of course work to close them.____ >>>>> >>>>> __ __ >>>>> >>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>> available under the most recent contract extension. This should >>>>> provide adequate time for any consultation needed and any >>>>> updates and/or final tuning necessary. I have attached a brief >>>>> report on that burn to this email. Steve, I will send you a more >>>>> detailed version that you can share inside Sightline as needed. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> Please let me know if you have any questions or concerns. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> While I will continue to be in touch as we close down the project, I >>>>> want to take this opportunity to thank everyone involved for all >>>>> their work. I am confident I speak for all of us at Linaro when I >>>>> say I hope we have the opportunity to work with Sightline >>>>> Applications again in the future.____ >>>>> >>>>> __ __ >>>>> >>>>> Kind regards,____ >>>>> >>>>> Paul____ >>>>> >>>>> -- ____ >>>>> >>>>> Linaro http://www.linaro.org/____ >>>>> >>>>> >>>>> >>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>> >>>>> T: +44 0771 377 8664 >>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>> IRC: pneuhardt____ >>>>> >>>>> __ __ >>>>> >>>>> >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> >>> >>> -- >>> With best wishes >>> Dmitry >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry >
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide-4000-...
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Im ag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/ 59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote:
Got it, thanks!
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 23, 2022 12:04 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 01:52, Kim Steiner wrote: > Hi Dmitry, > > I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would.
This sounds great!
> > I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: > [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 > > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > > Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me.
Probably there is some misunderstanding. On 17th of November i wrote: "1) I was able to reproduce the failure during the cold boot. I'm investigating it now."
On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
> > Thanks, > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Friday, November 18, 2022 12:42 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > First, I have updated the release branch. The changes included are: > > - fix warming up code in the thermal subsystem to behave more > aggressively > - add more warming up sources to the CPU and GPU devices > - add separate driver to use MX and CX power rails to warm up > the GPU > > Could you please give this release a test? > Meanwhile I will continue debugging the 'boot up reboot' issue. > > On 17/11/2022 15:35, Kim Steiner wrote: >> Hi Dmitry, >> In response to: >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? > > Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? > > If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' > > I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. > >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Wednesday, November 16, 2022 2:15 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> On 15/11/2022 20:15, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>> >>> 1.) wait 1 minute with power disconnected. >>> 2.) turn on power. >>> 3.) Usually get one of these: >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>> S - Boot Interface: UFS >>> S - Secure Boot: Off >>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>> 0x000760f4 = >>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >> >> I did a lot of testing. Short summary: >> >> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >> >> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >> >> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >> >>> >>> Thanks, >>> Kim >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 8:56 AM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>> jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: RE: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Dmitry, >>> >>> The build instructions work for me so I will forward them to Penguin Solutions. >>> >>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Kim Steiner kim.steiner@sightlineapplications.com >>> Sent: Tuesday, November 15, 2022 5:43 AM >>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>> Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Dmitry, >>> >>> I will try these instructions today! Thank you 😊 >>> >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Tuesday, November 15, 2022 5:05 AM >>> To: Jordan Holt jordan.holt@sightlineapplications.com >>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>> Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hello, Jordan, Kim, >>> >>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>> >>>> Hi Dmitry and Paul, >>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>> >>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>> >>>> Thank you, >>>> Jordan >>>> >>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>> Video Processing | he/him >>>> >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Thursday, November 10, 2022 3:34 PM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Dmitry, >>>> >>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>> >>>> Thanks, >>>> Kim >>>> -----Original Message----- >>>> From: Kim Steiner >>>> Sent: Friday, November 4, 2022 9:49 AM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>> Neuhardt paul.neuhardt@linaro.org >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Dmitry, >>>> >>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Friday, November 4, 2022 8:03 AM >>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>> kim.steiner@sightlineapplications.com >>>> Cc: sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Kim, >>>> >>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>> Kim, >>>>> >>>>> I had thought that the latest updates had been posted to >>>>> your repository. My apologies for the misunderstanding. I >>>>> will ask Dmitry to post his updates as soon as possible. >>>> >>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>> >>>>> >>>>> Paul >>>>> >>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>> <kim.steiner@sightlineapplications.com >>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>> >>>>> Hi Paul,____ >>>>> >>>>> __ __ >>>>> >>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>> I'll work on improving the warming of the >>>>> CPU/GPU then.”____ >>>>> >>>>> __ __ >>>>> >>>>> 2. We still have a very slow boot up time >>>>> (+2minutes).____ >>>>> >>>>> __ __ >>>>> >>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>> few minutes before stopping.____ >>>>> >>>>> __ __ >>>>> >>>>> __ __ >>>>> >>>>> As of Wednesday (with latest git repository changes), the above >>>>> issues existed and I do not plan on doing any more testing until I >>>>> see new changes or get something new to >>>>> test.____ >>>>> >>>>> __ __ >>>>> >>>>> I will inform Penguin Solutions that you are close so they can work >>>>> on patches for us to apply to our custom board >>>>> build.____ >>>>> >>>>> __ __ >>>>> >>>>> I would also like to again request a clear set of build instructions >>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>> correctly.____ >>>>> >>>>> __ __ >>>>> >>>>> Thanks,____ >>>>> >>>>> Kim____ >>>>> >>>>> __ __ >>>>> >>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>> mailto:paul.neuhardt@linaro.org> >>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>> *To:* sightlineapplications@lists.linaro.org >>>>> mailto:sightlineapplications@lists.linaro.org >>>>> *Subject:* [Sightlineapplications] Project >>>>> Status and Burn Report____ >>>>> >>>>> __ __ >>>>> >>>>> All,____ >>>>> >>>>> __ __ >>>>> >>>>> Dmitry has now delivered what he believes to be the final set of >>>>> updates to Sightline in support of this project. Sightline is in the >>>>> process of testing these deliverables and we expect that the results >>>>> will be at or close to what was expected. If there are still gaps, >>>>> we will of course work to close them.____ >>>>> >>>>> __ __ >>>>> >>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>> available under the most recent contract extension. This should >>>>> provide adequate time for any consultation needed and any >>>>> updates and/or final tuning necessary. I have attached a brief >>>>> report on that burn to this email. Steve, I will send you a more >>>>> detailed version that you can share inside Sightline as needed. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> Please let me know if you have any questions or concerns. >>>>> ____ >>>>> >>>>> __ __ >>>>> >>>>> While I will continue to be in touch as we close down the project, I >>>>> want to take this opportunity to thank everyone involved for all >>>>> their work. I am confident I speak for all of us at Linaro when I >>>>> say I hope we have the opportunity to work with Sightline >>>>> Applications again in the future.____ >>>>> >>>>> __ __ >>>>> >>>>> Kind regards,____ >>>>> >>>>> Paul____ >>>>> >>>>> -- ____ >>>>> >>>>> Linaro http://www.linaro.org/____ >>>>> >>>>> >>>>> >>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>> >>>>> T: +44 0771 377 8664 >>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>> IRC: pneuhardt____ >>>>> >>>>> __ __ >>>>> >>>>> >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> >>> >>> -- >>> With best wishes >>> Dmitry >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> >> _______________________________________________ >> Sightlineapplications mailing list -- >> sightlineapplications@lists.linaro.org >> To unsubscribe send an email to >> sightlineapplications-leave@lists.linaro.org > > -- > With best wishes > Dmitry >
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide-4000-...
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However: - I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
- If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.
- The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed: - How do I get the serial console? - Do I need to connect any power supply to the recovery board? the label "power" near J3 connector hints that - How can I test my own kernels? This is probably connected to the previous two questions. - I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Im ag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/ 59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote: > Got it, thanks! > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 23, 2022 12:04 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 23/11/2022 01:52, Kim Steiner wrote: >> Hi Dmitry, >> >> I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would. > > This sounds great! > >> >> I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: >> [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> >> Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me. > > Probably there is some misunderstanding. On 17th of November i wrote: > "1) I was able to reproduce the failure during the cold boot. I'm investigating it now." > > On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
> >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 18, 2022 12:42 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> First, I have updated the release branch. The changes included are: >> >> - fix warming up code in the thermal subsystem to behave more >> aggressively >> - add more warming up sources to the CPU and GPU devices >> - add separate driver to use MX and CX power rails to warm up >> the GPU >> >> Could you please give this release a test? >> Meanwhile I will continue debugging the 'boot up reboot' issue. >> >> On 17/11/2022 15:35, Kim Steiner wrote: >>> Hi Dmitry, >>> In response to: >>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>> >>> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? >> >> Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? >> >> If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' >> >> I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. >> >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Wednesday, November 16, 2022 2:15 PM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >>> Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Kim, >>> >>> On 15/11/2022 20:15, Kim Steiner wrote: >>>> Hi Dmitry, >>>> >>>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>>> >>>> 1.) wait 1 minute with power disconnected. >>>> 2.) turn on power. >>>> 3.) Usually get one of these: >>>> >>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>>> S - Boot Interface: UFS >>>> S - Secure Boot: Off >>>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>>> 0x000760f4 = >>>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >>> >>> I did a lot of testing. Short summary: >>> >>> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >>> >>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>> >>> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >>> >>>> >>>> Thanks, >>>> Kim >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Tuesday, November 15, 2022 8:56 AM >>>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>>> jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Dmitry, >>>> >>>> The build instructions work for me so I will forward them to Penguin Solutions. >>>> >>>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Tuesday, November 15, 2022 5:43 AM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>>> Holt jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Dmitry, >>>> >>>> I will try these instructions today! Thank you 😊 >>>> >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Tuesday, November 15, 2022 5:05 AM >>>> To: Jordan Holt jordan.holt@sightlineapplications.com >>>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>>> Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hello, Jordan, Kim, >>>> >>>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>>> >>>>> Hi Dmitry and Paul, >>>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>>> >>>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>>> >>>>> Thank you, >>>>> Jordan >>>>> >>>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>>> Video Processing | he/him >>>>> >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Thursday, November 10, 2022 3:34 PM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>> Neuhardt paul.neuhardt@linaro.org >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>> Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>>> >>>>> Thanks, >>>>> Kim >>>>> -----Original Message----- >>>>> From: Kim Steiner >>>>> Sent: Friday, November 4, 2022 9:49 AM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>> Neuhardt paul.neuhardt@linaro.org >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>>> >>>>> Thanks, >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>> Sent: Friday, November 4, 2022 8:03 AM >>>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>>> kim.steiner@sightlineapplications.com >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Kim, >>>>> >>>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>>> Kim, >>>>>> >>>>>> I had thought that the latest updates had been posted to >>>>>> your repository. My apologies for the misunderstanding. I >>>>>> will ask Dmitry to post his updates as soon as possible. >>>>> >>>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>>> >>>>>> >>>>>> Paul >>>>>> >>>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>>> <kim.steiner@sightlineapplications.com >>>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>>> >>>>>> Hi Paul,____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>>> I'll work on improving the warming of the >>>>>> CPU/GPU then.”____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 2. We still have a very slow boot up time >>>>>> (+2minutes).____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>>> few minutes before stopping.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> __ __ >>>>>> >>>>>> As of Wednesday (with latest git repository changes), the above >>>>>> issues existed and I do not plan on doing any more testing until I >>>>>> see new changes or get something new to >>>>>> test.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> I will inform Penguin Solutions that you are close so they can work >>>>>> on patches for us to apply to our custom board >>>>>> build.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> I would also like to again request a clear set of build instructions >>>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>>> correctly.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Thanks,____ >>>>>> >>>>>> Kim____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>>> mailto:paul.neuhardt@linaro.org> >>>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>>> *To:* sightlineapplications@lists.linaro.org >>>>>> mailto:sightlineapplications@lists.linaro.org >>>>>> *Subject:* [Sightlineapplications] Project >>>>>> Status and Burn Report____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> All,____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Dmitry has now delivered what he believes to be the final set of >>>>>> updates to Sightline in support of this project. Sightline is in the >>>>>> process of testing these deliverables and we expect that the results >>>>>> will be at or close to what was expected. If there are still gaps, >>>>>> we will of course work to close them.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>>> available under the most recent contract extension. This should >>>>>> provide adequate time for any consultation needed and any >>>>>> updates and/or final tuning necessary. I have attached a brief >>>>>> report on that burn to this email. Steve, I will send you a more >>>>>> detailed version that you can share inside Sightline as needed. >>>>>> ____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Please let me know if you have any questions or concerns. >>>>>> ____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> While I will continue to be in touch as we close down the project, I >>>>>> want to take this opportunity to thank everyone involved for all >>>>>> their work. I am confident I speak for all of us at Linaro when I >>>>>> say I hope we have the opportunity to work with Sightline >>>>>> Applications again in the future.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Kind regards,____ >>>>>> >>>>>> Paul____ >>>>>> >>>>>> -- ____ >>>>>> >>>>>> Linaro http://www.linaro.org/____ >>>>>> >>>>>> >>>>>> >>>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>>> >>>>>> T: +44 0771 377 8664 >>>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>>> IRC: pneuhardt____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Sightlineapplications mailing list -- >>>>>> sightlineapplications@lists.linaro.org >>>>>> To unsubscribe send an email to >>>>>> sightlineapplications-leave@lists.linaro.org >>>>> >>>>> -- >>>>> With best wishes >>>>> Dmitry >>>>> >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> > > -- > With best wishes > Dmitry >
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
Are you saying that you are using a Linux machine and not Windows? Panel+ only runs on Windows OS. I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board. You are NOT using the 0304 cable? I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC. I also have the micro-USB to USB A connected to the 4000-Recovery at J2 (and then connected to my PC). From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2." I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).
Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document). Then you can fastboot versions of your kernel.
If you could, it would be easiest if you took a picture(s) of your setup. Out of the items you mentioned that you aren't using, I think 0304 is needed. 0404 is only needed if you have an SLA-DIST board. I don't know what the USBto3pin is.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 19, 2023 11:34 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide -4000-OEM.pdf
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However: - I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
- If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.
- The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed: - How do I get the serial console? - Do I need to connect any power supply to the recovery board? the label "power" near J3 connector hints that - How can I test my own kernels? This is probably connected to the previous two questions. - I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote:
Hi Dmitry,
With this patch, I built per your instructions. I got this error when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) [200] HALT: reboot into dload mo
So I change the --pagesize to 4096 and built the image again and it worked. It looks like the db820c should use 4096 per this page: https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Im ag e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
I cycled power 15 or so times and only had one failed boot with the above patch:
[ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 S - IMAGE_VARIANT_STRING=M8996LAB S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 S - Boot Interface: UFS S - Secure Boot: Off S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 = 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number @ 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
I'm not sure if this boot failure is the same as the 4.14 boot failure or not: https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/ 59 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
Thanks,
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, November 24, 2022 11:16 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 23/11/2022 23:57, Kim Steiner wrote: > Got it, thanks! > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Wednesday, November 23, 2022 12:04 PM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 23/11/2022 01:52, Kim Steiner wrote: >> Hi Dmitry, >> >> I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would. > > This sounds great! > >> >> I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: >> [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 >> >> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >> >> Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me. > > Probably there is some misunderstanding. On 17th of November i wrote: > "1) I was able to reproduce the failure during the cold boot. I'm investigating it now." > > On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. "
It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch.
> >> >> Thanks, >> Kim >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Friday, November 18, 2022 12:42 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> First, I have updated the release branch. The changes included are: >> >> - fix warming up code in the thermal subsystem to behave more >> aggressively >> - add more warming up sources to the CPU and GPU devices >> - add separate driver to use MX and CX power rails to warm up >> the GPU >> >> Could you please give this release a test? >> Meanwhile I will continue debugging the 'boot up reboot' issue. >> >> On 17/11/2022 15:35, Kim Steiner wrote: >>> Hi Dmitry, >>> In response to: >>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>> >>> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? >> >> Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? >> >> If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' >> >> I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. >> >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Wednesday, November 16, 2022 2:15 PM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >>> Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Kim, >>> >>> On 15/11/2022 20:15, Kim Steiner wrote: >>>> Hi Dmitry, >>>> >>>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>>> >>>> 1.) wait 1 minute with power disconnected. >>>> 2.) turn on power. >>>> 3.) Usually get one of these: >>>> >>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>>> S - Boot Interface: UFS >>>> S - Secure Boot: Off >>>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>>> 0x000760f4 = >>>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >>> >>> I did a lot of testing. Short summary: >>> >>> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >>> >>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>> >>> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >>> >>>> >>>> Thanks, >>>> Kim >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Tuesday, November 15, 2022 8:56 AM >>>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>>> jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hi Dmitry, >>>> >>>> The build instructions work for me so I will forward them to Penguin Solutions. >>>> >>>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>> Sent: Tuesday, November 15, 2022 5:43 AM >>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>>> Holt jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Dmitry, >>>> >>>> I will try these instructions today! Thank you 😊 >>>> >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Tuesday, November 15, 2022 5:05 AM >>>> To: Jordan Holt jordan.holt@sightlineapplications.com >>>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>>> Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>> Burn Report >>>> >>>> Hello, Jordan, Kim, >>>> >>>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>>> >>>>> Hi Dmitry and Paul, >>>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>>> >>>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>>> >>>>> Thank you, >>>>> Jordan >>>>> >>>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>>> Video Processing | he/him >>>>> >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Thursday, November 10, 2022 3:34 PM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>> Neuhardt paul.neuhardt@linaro.org >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>> Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>>> >>>>> Thanks, >>>>> Kim >>>>> -----Original Message----- >>>>> From: Kim Steiner >>>>> Sent: Friday, November 4, 2022 9:49 AM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>> Neuhardt paul.neuhardt@linaro.org >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>>> >>>>> Thanks, >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>> Sent: Friday, November 4, 2022 8:03 AM >>>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>>> kim.steiner@sightlineapplications.com >>>>> Cc: sightlineapplications@lists.linaro.org >>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Kim, >>>>> >>>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>>> Kim, >>>>>> >>>>>> I had thought that the latest updates had been posted to >>>>>> your repository. My apologies for the misunderstanding. I >>>>>> will ask Dmitry to post his updates as soon as possible. >>>>> >>>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>>> >>>>>> >>>>>> Paul >>>>>> >>>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>>> <kim.steiner@sightlineapplications.com >>>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>>> >>>>>> Hi Paul,____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>>> I'll work on improving the warming of the >>>>>> CPU/GPU then.”____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 2. We still have a very slow boot up time >>>>>> (+2minutes).____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>>> few minutes before stopping.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> __ __ >>>>>> >>>>>> As of Wednesday (with latest git repository changes), the above >>>>>> issues existed and I do not plan on doing any more testing until I >>>>>> see new changes or get something new to >>>>>> test.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> I will inform Penguin Solutions that you are close so they can work >>>>>> on patches for us to apply to our custom board >>>>>> build.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> I would also like to again request a clear set of build instructions >>>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>>> correctly.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Thanks,____ >>>>>> >>>>>> Kim____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>>> mailto:paul.neuhardt@linaro.org> >>>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>>> *To:* sightlineapplications@lists.linaro.org >>>>>> mailto:sightlineapplications@lists.linaro.org >>>>>> *Subject:* [Sightlineapplications] Project >>>>>> Status and Burn Report____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> All,____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Dmitry has now delivered what he believes to be the final set of >>>>>> updates to Sightline in support of this project. Sightline is in the >>>>>> process of testing these deliverables and we expect that the results >>>>>> will be at or close to what was expected. If there are still gaps, >>>>>> we will of course work to close them.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>>> available under the most recent contract extension. This should >>>>>> provide adequate time for any consultation needed and any >>>>>> updates and/or final tuning necessary. I have attached a brief >>>>>> report on that burn to this email. Steve, I will send you a more >>>>>> detailed version that you can share inside Sightline as needed. >>>>>> ____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Please let me know if you have any questions or concerns. >>>>>> ____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> While I will continue to be in touch as we close down the project, I >>>>>> want to take this opportunity to thank everyone involved for all >>>>>> their work. I am confident I speak for all of us at Linaro when I >>>>>> say I hope we have the opportunity to work with Sightline >>>>>> Applications again in the future.____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> Kind regards,____ >>>>>> >>>>>> Paul____ >>>>>> >>>>>> -- ____ >>>>>> >>>>>> Linaro http://www.linaro.org/____ >>>>>> >>>>>> >>>>>> >>>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>>> >>>>>> T: +44 0771 377 8664 >>>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>>> IRC: pneuhardt____ >>>>>> >>>>>> __ __ >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Sightlineapplications mailing list -- >>>>>> sightlineapplications@lists.linaro.org >>>>>> To unsubscribe send an email to >>>>>> sightlineapplications-leave@lists.linaro.org >>>>> >>>>> -- >>>>> With best wishes >>>>> Dmitry >>>>> >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >>> _______________________________________________ >>> Sightlineapplications mailing list -- >>> sightlineapplications@lists.linaro.org >>> To unsubscribe send an email to >>> sightlineapplications-leave@lists.linaro.org >> >> -- >> With best wishes >> Dmitry >> > > -- > With best wishes > Dmitry >
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
All,
I'm shortening this thread a bit. The messages have gotten so big with all the replies that it is now too large for our email system to pass through without my manual approval each time. To try to prevent my availability and attention from being a bottleneck, I'm starting a new thread with the same subject but only the last few messages.
Paul
On Fri, 20 Jan 2023 at 16:41, Kim Steiner < kim.steiner@sightlineapplications.com> wrote:
Hi Dmitry,
Are you saying that you are using a Linux machine and not Windows? Panel+ only runs on Windows OS. I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board. You are NOT using the 0304 cable? I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC. I also have the micro-USB to USB A connected to the 4000-Recovery at J2 (and then connected to my PC). From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2." I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).
Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document). Then you can fastboot versions of your kernel.
If you could, it would be easiest if you took a picture(s) of your setup. Out of the items you mentioned that you aren't using, I think 0304 is needed. 0404 is only needed if you have an SLA-DIST board. I don't know what the USBto3pin is.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 19, 2023 11:34 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt < paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe
it was still confusing?
https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide -4000-OEM.pdf
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However:
- I attached the provided USB-Serial connector to the J4 on the "recovery"
board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
- If I try attaching the microUSB cable to the J2 connector on recovery
board, my laptop shows "usb port overcurrent" messages.
- The PanelPlus software seems to be available only for Windows machines.
I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed:
- How do I get the serial console?
- Do I need to connect any power supply to the recovery board? the label
"power" near J3 connector hints that
- How can I test my own kernels? This is probably connected to the
previous two questions.
- I have the following cables left unattached: 0304, 0504, 1505, 0402,
0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt <
paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt <
paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office
to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many
times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week
(cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit,
it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk
me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first
boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy
New Year!
Thanks, Kim
Hi Paul,
On Fri, 20 Jan 2023 at 19:09, Paul Neuhardt paul.neuhardt@linaro.org wrote:
All,
I'm shortening this thread a bit. The messages have gotten so big with all the replies that it is now too large for our email system to pass through without my manual approval each time. To try to prevent my availability and attention from being a bottleneck, I'm starting a new thread with the same subject but only the last few messages.
Paul
On Fri, 20 Jan 2023 at 16:41, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
Are you saying that you are using a Linux machine and not Windows? Panel+ only runs on Windows OS.
Yes, I don't have a Windows machine. Any chance of getting Panel+ to run under Wine? I can probably try debugging, what is the cause of the problem.
I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board. You are NOT using the 0304 cable? I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC. I also have the micro-USB to USB A connected to the 4000-Recovery at J2 (and then connected to my PC). From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2." I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).
I will try using a 3-pin + USB-serial next week.
Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document). Then you can fastboot versions of your kernel.
If you could, it would be easiest if you took a picture(s) of your setup. Out of the items you mentioned that you aren't using, I think 0304 is needed. 0404 is only needed if you have an SLA-DIST board. I don't know what the USBto3pin is.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 19, 2023 11:34 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide -4000-OEM.pdf
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However:
I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.
The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed:
- How do I get the serial console?
- Do I need to connect any power supply to the recovery board? the label "power" near J3 connector hints that
- How can I test my own kernels? This is probably connected to the previous two questions.
- I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
Hi Kim,
On 20/01/2023 18:41, Kim Steiner wrote:
Hi Dmitry,
Are you saying that you are using a Linux machine and not Windows? Panel+ only runs on Windows OS.
As my attempts to run Panel+ under Wine have failed up to now, I've got another laptop, which has Windows onboard. I'll try using today in the evening.
I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board. You are NOT using the 0304 cable? I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC. I also have the micro-USB to USB A connected to the 4000-Recovery at J2 (and then connected to my PC). From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2." I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).
Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document). Then you can fastboot versions of your kernel.
If you could, it would be easiest if you took a picture(s) of your setup. Out of the items you mentioned that you aren't using, I think 0304 is needed. 0404 is only needed if you have an SLA-DIST board. I don't know what the USBto3pin is.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 19, 2023 11:34 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide -4000-OEM.pdf
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However:
I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.
The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed:
- How do I get the serial console?
- Do I need to connect any power supply to the recovery board? the label "power" near J3 connector hints that
- How can I test my own kernels? This is probably connected to the previous two questions.
- I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote: > Hi Dmitry, > > With this patch, I built per your instructions. I got this error > when I flashed boot.img: [180] sys r13 0x00000000 r14 0x00000000 > [190] panic (caller 0x91637134): ASSERT FAILED at > (platform/msm_shared/mmc_wrapper.c:190): !(data_len % block_size) > [200] HALT: reboot into dload mo > > So I change the --pagesize to 4096 and built the image again and > it worked. It looks like the db820c should use 4096 per this page: > https://github.com/96boards/documentation/wiki/Dragonboard-Boot-Im > ag > e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
> > I cycled power 15 or so times and only had one failed boot with the above patch: > > [ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) > [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups > [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) > [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 > [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA > [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
> > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB > S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ 0x000760f4 > = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial Number > @ > 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = > 0x0000000000000000 > > I'm not sure if this boot failure is the same as the 4.14 boot > failure or not: > https://discuss.96boards.org/t/boot-failure-crash-during-the-boot/ > 59 > 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
> > Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
> > Thanks, > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Thursday, November 24, 2022 11:16 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 23/11/2022 23:57, Kim Steiner wrote: >> Got it, thanks! >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Wednesday, November 23, 2022 12:04 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >> Report >> >> Hi Kim, >> >> On 23/11/2022 01:52, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would. >> >> This sounds great! >> >>> >>> I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: >>> [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> >>> Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me. >> >> Probably there is some misunderstanding. On 17th of November i wrote: >> "1) I was able to reproduce the failure during the cold boot. I'm investigating it now." >> >> On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. " > > It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch. > >> >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 18, 2022 12:42 PM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >>> Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and Burn >>> Report >>> >>> Hi Kim, >>> >>> First, I have updated the release branch. The changes included are: >>> >>> - fix warming up code in the thermal subsystem to behave more >>> aggressively >>> - add more warming up sources to the CPU and GPU devices >>> - add separate driver to use MX and CX power rails to warm up >>> the GPU >>> >>> Could you please give this release a test? >>> Meanwhile I will continue debugging the 'boot up reboot' issue. >>> >>> On 17/11/2022 15:35, Kim Steiner wrote: >>>> Hi Dmitry, >>>> In response to: >>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>> >>>> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? >>> >>> Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? >>> >>> If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' >>> >>> I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. >>> >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Wednesday, November 16, 2022 2:15 PM >>>> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >>>> Holt jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Kim, >>>> >>>> On 15/11/2022 20:15, Kim Steiner wrote: >>>>> Hi Dmitry, >>>>> >>>>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>>>> >>>>> 1.) wait 1 minute with power disconnected. >>>>> 2.) turn on power. >>>>> 3.) Usually get one of these: >>>>> >>>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>>>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>>>> S - Boot Interface: UFS >>>>> S - Secure Boot: Off >>>>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>>>> 0x000760f4 = >>>>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >>>> >>>> I did a lot of testing. Short summary: >>>> >>>> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >>>> >>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>> >>>> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >>>> >>>>> >>>>> Thanks, >>>>> Kim >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Tuesday, November 15, 2022 8:56 AM >>>>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>>>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>>>> jordan.holt@sightlineapplications.com >>>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> The build instructions work for me so I will forward them to Penguin Solutions. >>>>> >>>>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>>>> >>>>> Thanks, >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Tuesday, November 15, 2022 5:43 AM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>>>> Holt jordan.holt@sightlineapplications.com >>>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>> Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> I will try these instructions today! Thank you 😊 >>>>> >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>> Sent: Tuesday, November 15, 2022 5:05 AM >>>>> To: Jordan Holt jordan.holt@sightlineapplications.com >>>>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; Paul >>>>> Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hello, Jordan, Kim, >>>>> >>>>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>>>> >>>>>> Hi Dmitry and Paul, >>>>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>>>> >>>>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>>>> >>>>>> Thank you, >>>>>> Jordan >>>>>> >>>>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>>>> Video Processing | he/him >>>>>> >>>>>> -----Original Message----- >>>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>>> Sent: Thursday, November 10, 2022 3:34 PM >>>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>>> Neuhardt paul.neuhardt@linaro.org >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>>> Report >>>>>> >>>>>> Hi Dmitry, >>>>>> >>>>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>>>> >>>>>> Thanks, >>>>>> Kim >>>>>> -----Original Message----- >>>>>> From: Kim Steiner >>>>>> Sent: Friday, November 4, 2022 9:49 AM >>>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>>> Neuhardt paul.neuhardt@linaro.org >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>>> Burn Report >>>>>> >>>>>> Hi Dmitry, >>>>>> >>>>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>>>> >>>>>> Thanks, >>>>>> Kim >>>>>> >>>>>> -----Original Message----- >>>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>>> Sent: Friday, November 4, 2022 8:03 AM >>>>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>>>> kim.steiner@sightlineapplications.com >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>>> Burn Report >>>>>> >>>>>> Hi Kim, >>>>>> >>>>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>>>> Kim, >>>>>>> >>>>>>> I had thought that the latest updates had been posted to >>>>>>> your repository. My apologies for the misunderstanding. I >>>>>>> will ask Dmitry to post his updates as soon as possible. >>>>>> >>>>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>>>> >>>>>>> >>>>>>> Paul >>>>>>> >>>>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>>>> <kim.steiner@sightlineapplications.com >>>>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>>>> >>>>>>> Hi Paul,____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>>>> I'll work on improving the warming of the >>>>>>> CPU/GPU then.”____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 2. We still have a very slow boot up time >>>>>>> (+2minutes).____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>>>> few minutes before stopping.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> As of Wednesday (with latest git repository changes), the above >>>>>>> issues existed and I do not plan on doing any more testing until I >>>>>>> see new changes or get something new to >>>>>>> test.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> I will inform Penguin Solutions that you are close so they can work >>>>>>> on patches for us to apply to our custom board >>>>>>> build.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> I would also like to again request a clear set of build instructions >>>>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>>>> correctly.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Thanks,____ >>>>>>> >>>>>>> Kim____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>>>> mailto:paul.neuhardt@linaro.org> >>>>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>>>> *To:* sightlineapplications@lists.linaro.org >>>>>>> mailto:sightlineapplications@lists.linaro.org >>>>>>> *Subject:* [Sightlineapplications] Project >>>>>>> Status and Burn Report____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> All,____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Dmitry has now delivered what he believes to be the final set of >>>>>>> updates to Sightline in support of this project. Sightline is in the >>>>>>> process of testing these deliverables and we expect that the results >>>>>>> will be at or close to what was expected. If there are still gaps, >>>>>>> we will of course work to close them.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>>>> available under the most recent contract extension. This should >>>>>>> provide adequate time for any consultation needed and any >>>>>>> updates and/or final tuning necessary. I have attached a brief >>>>>>> report on that burn to this email. Steve, I will send you a more >>>>>>> detailed version that you can share inside Sightline as needed. >>>>>>> ____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Please let me know if you have any questions or concerns. >>>>>>> ____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> While I will continue to be in touch as we close down the project, I >>>>>>> want to take this opportunity to thank everyone involved for all >>>>>>> their work. I am confident I speak for all of us at Linaro when I >>>>>>> say I hope we have the opportunity to work with Sightline >>>>>>> Applications again in the future.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Kind regards,____ >>>>>>> >>>>>>> Paul____ >>>>>>> >>>>>>> -- ____ >>>>>>> >>>>>>> Linaro http://www.linaro.org/____ >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>>>> >>>>>>> T: +44 0771 377 8664 >>>>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>>>> IRC: pneuhardt____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Sightlineapplications mailing list -- >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> To unsubscribe send an email to >>>>>>> sightlineapplications-leave@lists.linaro.org >>>>>> >>>>>> -- >>>>>> With best wishes >>>>>> Dmitry >>>>>> >>>>>> _______________________________________________ >>>>>> Sightlineapplications mailing list -- >>>>>> sightlineapplications@lists.linaro.org >>>>>> To unsubscribe send an email to >>>>>> sightlineapplications-leave@lists.linaro.org >>>>> >>>>> >>>>> >>>>> -- >>>>> With best wishes >>>>> Dmitry >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >> >> -- >> With best wishes >> Dmitry >> > > -- > With best wishes > Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, January 23, 2023 3:05 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/01/2023 18:41, Kim Steiner wrote:
Hi Dmitry,
Are you saying that you are using a Linux machine and not Windows? Panel+ only runs on Windows OS.
As my attempts to run Panel+ under Wine have failed up to now, I've got another laptop, which has Windows onboard. I'll try using today in the evening.
I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board. You are NOT using the 0304 cable? I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC. I also have the micro-USB to USB A connected to the 4000-Recovery at J2 (and then connected to my PC). From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2." I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).
Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document). Then you can fastboot versions of your kernel.
If you could, it would be easiest if you took a picture(s) of your setup. Out of the items you mentioned that you aren't using, I think 0304 is needed. 0404 is only needed if you have an SLA-DIST board. I don't know what the USBto3pin is.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 19, 2023 11:34 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim
On 17/01/2023 16:17, Kim Steiner wrote:
Hi Dmitry,
Also, did you take a look at the startup guide for the 4000? Or maybe it was still confusing? https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guid e -4000-OEM.pdf
Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).
However:
I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?
If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.
The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.
So, few questions to proceed:
- How do I get the serial console?
- Do I need to connect any power supply to the recovery board? the
label "power" near J3 connector hints that
- How can I test my own kernels? This is probably connected to the previous two questions.
- I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, January 13, 2023 5:50 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Comments ** below.
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, January 12, 2023 6:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
I hope you feel better now! ** yes, feeling better! Thank you. We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet. Once we get the test area set up, then that will begin (next week).
On 29/12/2022 16:19, Kim Steiner wrote:
Hi Dmitry,
Happy Holidays to you too! I am still dealing with this cold and am not able to go into the office to do any testing this week. I am working remotely so will do some power cycles/reboots on the DB820c today. I hope to see your same results 😊
Were you able to do resume the boot and cpufreq tests by chance? ** I feel confident boot is working successfully and have rebooted many times. I also below the cpufreq is working as expected. I have tested both the boot and cpufreq on the DB820c and our custom board.
I had also been running our custom board with the latest from last week (cpufreq changes). With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot. We think this is because the GPU is doing some frequency changes on the fly. In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations. Do you have any suggestions? Can we just use a single GPU frequency?
I'll look into this during the forthcoming week.
An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
** yes! Someone here can help walk you through the assembly and first boot. Should I set up a meeting? Which day works for you?
I will be out Friday-Monday for the New Year's holiday. Have a Happy New Year!
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, December 27, 2022 3:15 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
Happy holidays! I hope you feel better now.
On 22/12/2022 19:45, Kim Steiner wrote:
Hi Dmitry,
I did about 20 or so full power cycles (turn off board, wait 10 seconds, power on board) and reboots. I see the attached boot failures (3 different ones).
Finally I was able to track down and the bootup issues. I have updated the release branch with the fixes. Currently this kernel has survived around ~1000 bootups without any hangs! (I hope I won't burn the board by doing constant reboots).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, December 21, 2022 11:48 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 20/12/2022 19:01, Kim Steiner wrote:
Hi Dmitry,
With these cpufreq changes to the branch, can I test the original GPU temperature issue? I don't think I mentioned it, but boot time seems faster now with the cpufreq patch you last sent 😊
I have pushed a series of fixes to the interconnect driver. With this kernel after lots of tries I can not reproduce the hang at the boot time anymore.
BTW: any progress on shipping your hardware?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, December 19, 2022 4:45 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On Sat, 3 Dec 2022 at 00:19, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
It was the 'maxcpus=2' cmdline argument. I removed it to get 4 cpu cores. On our system we will need all 4 cores. Also, we will need to be able to set the cores to atleast 1GHz. We used these commands in 4.14 kernel: cpufreq-set --cpu 0 --governor performance --min 1000Mhz --max 1000Mhz cpufreq-set --cpu 2 --governor performance --min 1000Mhz --max 1000Mhz
I have updated the release branch with the patches that fix the cpufreq issue.
Using this kernel and these commands I can set the required frequencies:
# cpufreq-info | grep current current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware). current policy: frequency should be within 1.04 GHz and 1.04 GHz. current CPU frequency is 1.04 GHz (asserted by call to hardware).
but they do not work in the 5.15 branch.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, December 2, 2022 12:38 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
When I run 'nproc --all', it reports 4 cpu cores. If I issue 'cpufreq-info', I only see 2. Is there a way to see all 4 cpu cores? It looks like the device tree is ok and I don't see any cpu errors in 'dmesg' (that I can tell are errors).
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, November 30, 2022 12:22 PM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 28/11/2022 22:19, Kim Steiner wrote: > Hi Dmitry, > > With this patch, I built per your instructions. I got this > error when I flashed boot.img: [180] sys r13 0x00000000 r14 > 0x00000000 [190] panic (caller 0x91637134): ASSERT FAILED at > (platform/msm_shared/mmc_wrapper.c:190): !(data_len % > block_size) [200] HALT: reboot into dload mo > > So I change the --pagesize to 4096 and built the image again and > it worked. It looks like the db820c should use 4096 per this page: > https://github.com/96boards/documentation/wiki/Dragonboard-Boot- > Im > ag > e
Maybe there is a difference in the mkbootimg version. I have been using --pagesize 2048 here, see the attached build script that I'm using here.
If 4096 works for you, let's use it.
> > I cycled power 15 or so times and only had one failed boot with the above patch: > > [ 2.794094] arm-smmu 1600000.iommu: (IDR0.CTTW overridden by FW configuration) > [ 2.799742] arm-smmu 1600000.iommu: stream matching with 15 register groups > [ 2.806937] arm-smmu 1600000.iommu: 12 context banks (0 stage-2 only) > [ 2.814128] arm-smmu 1600000.iommu: Supported page sizes: 0x63315000 > [ 2.820400] arm-smmu 1600000.iommu: Stage-1: 36-bit VA -> 36-bit IPA > [ 2.884395] Bluetooth: hci0: Frame reassembly failed (-84)
Interesting. I'll run additional tests on my side.
> > Format: Log Type - Time(microsec) - Message - Optional Info Log Type: > B - Since Boot(Power On Reset), D - Delta, S - Statistic S - > QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 > S - IMAGE_VARIANT_STRING=M8996LAB S - > OEM_IMAGE_VERSION_STRING=crm-ubuntu68 > S - Boot Interface: UFS > S - Secure Boot: Off > S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ > 0x000760f4 = > 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 S - Serial > Number @ > 0x00074138 = 0xbe8b8597 S - OEM Config Row 0 @ 0x00074188 = > 0x0000000000000000 > > I'm not sure if this boot failure is the same as the 4.14 boot > failure or not: > https://discuss.96boards.org/t/boot-failure-crash-during-the-boo > t/ > 59 > 31
No, it looks like a different kind of issue. The reported boot failures happened because of the cpufreq driver and the CPUs being not being properly powered.
> > Also, would it be possible for me to get your boot.img to compare with the one I built?
I have uploaded my image to: [1]
[1] https://fileserver.linaro.org/s/S27PALCCAN2xAXs
> > Thanks, > > Kim > > -----Original Message----- > From: Dmitry Baryshkov dmitry.baryshkov@linaro.org > Sent: Thursday, November 24, 2022 11:16 AM > To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan > Holt jordan.holt@sightlineapplications.com > Cc: Paul Neuhardt paul.neuhardt@linaro.org; > sightlineapplications@lists.linaro.org > Subject: Re: [Sightlineapplications] Re: Project Status and Burn > Report > > Hi Kim, > > On 23/11/2022 23:57, Kim Steiner wrote: >> Got it, thanks! >> >> -----Original Message----- >> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >> Sent: Wednesday, November 23, 2022 12:04 PM >> To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan >> Holt jordan.holt@sightlineapplications.com >> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >> sightlineapplications@lists.linaro.org >> Subject: Re: [Sightlineapplications] Re: Project Status and >> Burn Report >> >> Hi Kim, >> >> On 23/11/2022 01:52, Kim Steiner wrote: >>> Hi Dmitry, >>> >>> I ran our usual temp test with the latest and did not see the gpu failure. We are going to run more thorough of a test next week (full temp range). The glxgears application remains running if I run it from the serial debug window just as you said it would. >> >> This sounds great! >> >>> >>> I haven't noticed any improvement to the booting of the DB820c. About 50% of the time it stops at around 5seconds and prints this: >>> [ 5.640755] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4 >>> >>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S - >>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>> >>> Could you send me your boot.img? It is odd that you do not have the same booting issue as me. I would like to confirm that your image works for me. >> >> Probably there is some misunderstanding. On 17th of November i wrote: >> "1) I was able to reproduce the failure during the cold boot. I'm investigating it now." >> >> On 18th of November I again stated that "Meanwhile I will continue debugging the 'boot up reboot' issue. " > > It took me a while, as I had to 'cool' the board between boots. With the attached patch I can no longer reproduce the reboots during the cold booting (first boot) the board. Could you please give it a try on your side too? It it works for you, I will push corresponding changes to the kernel branch. > >> >>> >>> Thanks, >>> Kim >>> >>> -----Original Message----- >>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>> Sent: Friday, November 18, 2022 12:42 PM >>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>> Jordan Holt jordan.holt@sightlineapplications.com >>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>> sightlineapplications@lists.linaro.org >>> Subject: Re: [Sightlineapplications] Re: Project Status and >>> Burn Report >>> >>> Hi Kim, >>> >>> First, I have updated the release branch. The changes included are: >>> >>> - fix warming up code in the thermal subsystem to behave more >>> aggressively >>> - add more warming up sources to the CPU and GPU devices >>> - add separate driver to use MX and CX power rails to warm up >>> the GPU >>> >>> Could you please give this release a test? >>> Meanwhile I will continue debugging the 'boot up reboot' issue. >>> >>> On 17/11/2022 15:35, Kim Steiner wrote: >>>> Hi Dmitry, >>>> In response to: >>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>> >>>> What I observe in the serial window is that I see the glxgears process with the 'ps' command and after a few minutes 'ps' shows no glxgears in the process list. Does this sound correct to you? >>> >>> Yes, this sounds correct. I was just trying to understand if this happens in the cold room test or in the normal working case? Do you see any output in the terminal in such case? >>> >>> If you need, you can run glxgears from the serial console by using 'XAUTHORITY=/home/linaro/.Xauthority DISPLAY=:0 glxgears' >>> >>> I'm asking since I've executed several overnight tests which included running the glxgears for hours without any interruption. >>> >>>> >>>> Thanks, >>>> Kim >>>> >>>> -----Original Message----- >>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>> Sent: Wednesday, November 16, 2022 2:15 PM >>>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>>> Jordan Holt jordan.holt@sightlineapplications.com >>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>> sightlineapplications@lists.linaro.org >>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>> Report >>>> >>>> Hi Kim, >>>> >>>> On 15/11/2022 20:15, Kim Steiner wrote: >>>>> Hi Dmitry, >>>>> >>>>> In doing more testing, I cannot get the DB820c to fully boot if I wait a while to turn on power: >>>>> >>>>> 1.) wait 1 minute with power disconnected. >>>>> 2.) turn on power. >>>>> 3.) Usually get one of these: >>>>> >>>>> Format: Log Type - Time(microsec) - Message - Optional Info Log Type: >>>>> B - Since Boot(Power On Reset), D - Delta, S - Statistic S >>>>> - >>>>> QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301 >>>>> S - IMAGE_VARIANT_STRING=M8996LAB S - >>>>> OEM_IMAGE_VERSION_STRING=crm-ubuntu68 >>>>> S - Boot Interface: UFS >>>>> S - Secure Boot: Off >>>>> S - Boot Config @ 0x00076044 = 0x000001c9 S - JTAG ID @ >>>>> 0x000760f4 = >>>>> 0x4003e0e1 S - OEM ID @ 0x000760f8 = 0x00000000 >>>> >>>> I did a lot of testing. Short summary: >>>> >>>> 1) I was able to reproduce the failure during the cold boot. I'm investigating it now. >>>> >>>> 2) If the board is in normal conditions, then glxgears can run like forever. I didn't see any interruption (X11 can blank the screen which would nearly stop glxgears, but that's another story. I think you are running tests with X11 blanking disabled). >>>> >>>> 3) I'm working on implementing the additional heating for the low temperatures using the PMIC regulators (MX and CX power domains). >>>> >>>>> >>>>> Thanks, >>>>> Kim >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Tuesday, November 15, 2022 8:56 AM >>>>> To: Kim Steiner kim.steiner@sightlineapplications.com; >>>>> Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt >>>>> jordan.holt@sightlineapplications.com >>>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> The build instructions work for me so I will forward them to Penguin Solutions. >>>>> >>>>> Are you still working on the CPU/GPU messaging? It looks like boot time is quicker (~40s). Did you look into the glxgears application not running for very long? >>>>> >>>>> Thanks, >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>> Sent: Tuesday, November 15, 2022 5:43 AM >>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan >>>>> Holt jordan.holt@sightlineapplications.com >>>>> Cc: Paul Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: [Sightlineapplications] Re: Project Status and Burn >>>>> Report >>>>> >>>>> Hi Dmitry, >>>>> >>>>> I will try these instructions today! Thank you 😊 >>>>> >>>>> Kim >>>>> >>>>> -----Original Message----- >>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>> Sent: Tuesday, November 15, 2022 5:05 AM >>>>> To: Jordan Holt jordan.holt@sightlineapplications.com >>>>> Cc: Kim Steiner kim.steiner@sightlineapplications.com; >>>>> Paul Neuhardt paul.neuhardt@linaro.org; >>>>> sightlineapplications@lists.linaro.org >>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>> Burn Report >>>>> >>>>> Hello, Jordan, Kim, >>>>> >>>>> On Tue, 15 Nov 2022 at 00:39, Jordan Holt jordan.holt@sightlineapplications.com wrote: >>>>>> >>>>>> Hi Dmitry and Paul, >>>>>> Any chance to get these build instructions? We would like to help Penguin to move forward. >>>>> >>>>> I have updated the kernel branch with board-specific defconfig. The build instructions are attached to this email. >>>>> >>>>>> Thank you, >>>>>> Jordan >>>>>> >>>>>> Jordan Holt | CTO | SightLine Applications Inc. | Onboard >>>>>> Video Processing | he/him >>>>>> >>>>>> -----Original Message----- >>>>>> From: Kim Steiner kim.steiner@sightlineapplications.com >>>>>> Sent: Thursday, November 10, 2022 3:34 PM >>>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>>> Neuhardt paul.neuhardt@linaro.org >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: [Sightlineapplications] Re: Project Status and >>>>>> Burn Report >>>>>> >>>>>> Hi Dmitry, >>>>>> >>>>>> I asked Penguin Solutions to start looking at creating a patch for us so they are trying to build/install the 5.15 kernel with the work you did so far. They would like some build instructions as well as us. They would also like to know the exact package name of the 11.2 compiler that you are using. I am using gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu. Is this the same package you are using? >>>>>> >>>>>> Thanks, >>>>>> Kim >>>>>> -----Original Message----- >>>>>> From: Kim Steiner >>>>>> Sent: Friday, November 4, 2022 9:49 AM >>>>>> To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Paul >>>>>> Neuhardt paul.neuhardt@linaro.org >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: RE: [Sightlineapplications] Re: Project Status and >>>>>> Burn Report >>>>>> >>>>>> Hi Dmitry, >>>>>> >>>>>> Yes, on Wednesday I tested your latest changes to the repo and had the issues mentioned to the group. I will wait for new updates to test. >>>>>> >>>>>> Thanks, >>>>>> Kim >>>>>> >>>>>> -----Original Message----- >>>>>> From: Dmitry Baryshkov dmitry.baryshkov@linaro.org >>>>>> Sent: Friday, November 4, 2022 8:03 AM >>>>>> To: Paul Neuhardt paul.neuhardt@linaro.org; Kim Steiner >>>>>> kim.steiner@sightlineapplications.com >>>>>> Cc: sightlineapplications@lists.linaro.org >>>>>> Subject: Re: [Sightlineapplications] Re: Project Status and >>>>>> Burn Report >>>>>> >>>>>> Hi Kim, >>>>>> >>>>>> On 04/11/2022 17:39, Paul Neuhardt wrote: >>>>>>> Kim, >>>>>>> >>>>>>> I had thought that the latest updates had been posted to >>>>>>> your repository. My apologies for the misunderstanding. I >>>>>>> will ask Dmitry to post his updates as soon as possible. >>>>>> >>>>>> The most recent code is in the repo. I'll update the repo as soon as I have any updates from my side, including the heating fine-tuning, etc. >>>>>> >>>>>>> >>>>>>> Paul >>>>>>> >>>>>>> On Fri, 4 Nov 2022 at 14:31, Kim Steiner >>>>>>> <kim.steiner@sightlineapplications.com >>>>>>> mailto:kim.steiner@sightlineapplications.com> wrote: >>>>>>> >>>>>>> Hi Paul,____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 1. In an email to Dmitry on 11/2/2022, I informed him that the gpu >>>>>>> temp issue may not be fixed. He stated “Thank you for the test. >>>>>>> I'll work on improving the warming of >>>>>>> the CPU/GPU then.”____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 2. We still have a very slow boot up time >>>>>>> (+2minutes).____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> 3. I informed Dmitry that the glxgears application only runs for a >>>>>>> few minutes before stopping.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> As of Wednesday (with latest git repository changes), the above >>>>>>> issues existed and I do not plan on doing any more testing until I >>>>>>> see new changes or get something new to >>>>>>> test.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> I will inform Penguin Solutions that you are close so they can work >>>>>>> on patches for us to apply to our custom >>>>>>> board build.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> I would also like to again request a clear set of build instructions >>>>>>> (changes to .config, compiler, initram…) so that I can build/test >>>>>>> correctly.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Thanks,____ >>>>>>> >>>>>>> Kim____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> *From:* Paul Neuhardt <paul.neuhardt@linaro.org >>>>>>> mailto:paul.neuhardt@linaro.org> >>>>>>> *Sent:* Friday, November 4, 2022 7:05 AM >>>>>>> *To:* sightlineapplications@lists.linaro.org >>>>>>> mailto:sightlineapplications@lists.linaro.org >>>>>>> *Subject:* [Sightlineapplications] Project >>>>>>> Status and Burn Report____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> All,____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Dmitry has now delivered what he believes to be the final set of >>>>>>> updates to Sightline in support of this project. Sightline is in the >>>>>>> process of testing these deliverables and we expect that the results >>>>>>> will be at or close to what was expected. If there are still gaps, >>>>>>> we will of course work to close them.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> As of today, there are still 13.5 hours of Dmitry's time left >>>>>>> available under the most recent contract extension. This should >>>>>>> provide adequate time for any consultation needed and any >>>>>>> updates and/or final tuning necessary. I have attached a brief >>>>>>> report on that burn to this email. Steve, I will send you a more >>>>>>> detailed version that you can share inside Sightline as needed. >>>>>>> ____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Please let me know if you have any questions or concerns. >>>>>>> ____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> While I will continue to be in touch as we close down the project, I >>>>>>> want to take this opportunity to thank everyone involved for all >>>>>>> their work. I am confident I speak for all of us at Linaro when I >>>>>>> say I hope we have the opportunity to work with Sightline >>>>>>> Applications again in the future.____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> Kind regards,____ >>>>>>> >>>>>>> Paul____ >>>>>>> >>>>>>> -- ____ >>>>>>> >>>>>>> Linaro http://www.linaro.org/____ >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Paul Neuhardt*|/Sr. Program Manager/____ >>>>>>> >>>>>>> T: +44 0771 377 8664 >>>>>>> paul.neuhardt@linaro.org mailto:glen.valante@linaro.org >>>>>>> IRC: pneuhardt____ >>>>>>> >>>>>>> __ __ >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Sightlineapplications mailing list -- >>>>>>> sightlineapplications@lists.linaro.org >>>>>>> To unsubscribe send an email to >>>>>>> sightlineapplications-leave@lists.linaro.org >>>>>> >>>>>> -- >>>>>> With best wishes >>>>>> Dmitry >>>>>> >>>>>> _______________________________________________ >>>>>> Sightlineapplications mailing list -- >>>>>> sightlineapplications@lists.linaro.org >>>>>> To unsubscribe send an email to >>>>>> sightlineapplications-leave@lists.linaro.org >>>>> >>>>> >>>>> >>>>> -- >>>>> With best wishes >>>>> Dmitry >>>>> _______________________________________________ >>>>> Sightlineapplications mailing list -- >>>>> sightlineapplications@lists.linaro.org >>>>> To unsubscribe send an email to >>>>> sightlineapplications-leave@lists.linaro.org >>>> >>>> -- >>>> With best wishes >>>> Dmitry >>>> >>>> _______________________________________________ >>>> Sightlineapplications mailing list -- >>>> sightlineapplications@lists.linaro.org >>>> To unsubscribe send an email to >>>> sightlineapplications-leave@lists.linaro.org >>> >>> -- >>> With best wishes >>> Dmitry >>> >> >> -- >> With best wishes >> Dmitry >> > > -- > With best wishes > Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
Just composite video.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, January 25, 2023 9:50 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
-- With best wishes Dmitry
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, January 25, 2023 9:50 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
[cid:image001.png@01D930A6.595EF500]
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson steve.olson@sightlineapplications.com Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
1. I put a 5.15 kernel 4000 installer here: https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0 2. Our device tree sources, you can find here: https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0 3. I'm not 100% on what you will need if you use your 5.15 kernel build and want to run media-ctl and v4l2-ctl tools from the command line. What works for me is to
A. Run our VTNext_ARM64_Release.out - this is doing some FPGA reset and setup of GPIOs
B. sudo media-ctl -d /dev/media0 -l '"msm_csiphy2":1->"msm_csid1":0[1],"msm_csid1":1->"msm_ispif1":0[1],"msm_ispif1":1->"msm_vfe0_rdi1":0[1]'
1. sudo media-ctl -d /dev/media0 -V '"mt9034 5-003a":0[fmt:UYVY2X8/1280x720],"msm_csiphy2":0[fmt:UYVY2X8/1280x720],"msm_csid1":0[fmt:UYVY2X8/1280x720],"msm_ispif1":0[fmt:UYVY2X8/1280x720],"msm_vfe0_rdi1":0[fmt:UYVY2X8/1280x720]'
1. sudo v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat='UYVY' -d /dev/video1
1. v4l2-ctl --stream-mmap=4 --verbose -d /dev/video1
1. polling_ms is in this file - drivers/gpu/drm/msm/msm_gpu_devfreq.c:90: .polling_ms = 50,
If #3 does not work for you, then let me know and I will proceed with getting access to our kernel repository.
Thanks, Kim
From: Jordan Holt jordan.holt@sightlineapplications.com Sent: Wednesday, January 25, 2023 10:20 AM To: Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
I tried having a single GPU frequency in the opp table, but when I run our software I get these messages and I don't think the encoder/display is working: *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9)
Thanks, Kim
From: Jordan Holt jordan.holt@sightlineapplications.com Sent: Wednesday, January 25, 2023 10:20 AM To: Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
You had asked yesterday about the boot time and I said that the 5.15 version was comparable to the 4.14 version of kernel. I did some more side by side comparison and the 5.15 boot up time is 0-6 seconds slower than the 4.14. It seems the 5.15 boot loader portion is the slow part and gets "stuck" here for longer than the 4.14 version:
[630] booting linux @ 0x80080000, ramdisk @ 0x92493000 (18740546), tags/device tree @ 0x85600000 [640] Jumping to kernel via monitor
Thanks, Kim
From: Kim Steiner Sent: Wednesday, January 25, 2023 3:38 PM To: Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I tried having a single GPU frequency in the opp table, but when I run our software I get these messages and I don't think the encoder/display is working: *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9) Buffer : 0xffffffffffffffff *** ERROR -1 creating dumb buffer *** *** ERROR -1 mapping dumb buffer *** Could not map buffer exported through PRIME : Bad file descriptor (9)
Thanks, Kim
From: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:20 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
On 26/01/2023 17:52, Kim Steiner wrote:
Hi Dmitry,
You had asked yesterday about the boot time and I said that the 5.15 version was comparable to the 4.14 version of kernel. I did some more side by side comparison and the 5.15 boot up time is 0-6 seconds slower than the 4.14. It seems the 5.15 boot loader portion is the slow part and gets “stuck” here for longer than the 4.14 version:
Ack, thanks for the comparison. I think this happens to the kernel growth, I'll check if we can disable more in-kernel drivers.
[630] booting linux @ 0x80080000, ramdisk @ 0x92493000 (18740546), tags/device tree @ 0x85600000
[640] Jumping to kernel via monitor
Thanks,
Kim
*From:* Kim Steiner *Sent:* Wednesday, January 25, 2023 3:38 PM *To:* Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org *Cc:* Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
I tried having a single GPU frequency in the opp table, but when I run our software I get these messages and I don’t think the encoder/display is working:
*** ERROR -1 creating dumb buffer ***
*** ERROR -1 mapping dumb buffer ***
Could not map buffer exported through PRIME : Bad file descriptor (9)
Buffer : 0xffffffffffffffff
*** ERROR -1 creating dumb buffer ***
*** ERROR -1 mapping dumb buffer ***
Could not map buffer exported through PRIME : Bad file descriptor (9)
Buffer : 0xffffffffffffffff
*** ERROR -1 creating dumb buffer ***
*** ERROR -1 mapping dumb buffer ***
Could not map buffer exported through PRIME : Bad file descriptor (9)
Buffer : 0xffffffffffffffff
*** ERROR -1 creating dumb buffer ***
*** ERROR -1 mapping dumb buffer ***
Could not map buffer exported through PRIME : Bad file descriptor (9)
Thanks,
Kim
*From:* Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com> *Sent:* Wednesday, January 25, 2023 10:20 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is “being held for review”.
*Jordan Holt | **CTO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him | 503 724-9727**
Please note our *NEW PORTLAND ADDRESS* is:
/5711 S Hood Ave., Suite A/
/Portland, OR 97239/
*From:* Jordan Holt *Sent:* Wednesday, January 25, 2023 10:18 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to *System* then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.com http://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to
try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org
mailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com
mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>;
sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our
custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible
opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org mailto:sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
Did you receive the new hd-sdi camera? Are you able to get video?
Have you looked into how to use a single GPU frequency in the 5.15 kernel?
Thanks, Kim
From: Kim Steiner Sent: Wednesday, January 25, 2023 12:02 PM To: Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
1. I put a 5.15 kernel 4000 installer here: https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0 2. Our device tree sources, you can find here: https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0 3. I'm not 100% on what you will need if you use your 5.15 kernel build and want to run media-ctl and v4l2-ctl tools from the command line. What works for me is to
A. Run our VTNext_ARM64_Release.out - this is doing some FPGA reset and setup of GPIOs
B. sudo media-ctl -d /dev/media0 -l '"msm_csiphy2":1->"msm_csid1":0[1],"msm_csid1":1->"msm_ispif1":0[1],"msm_ispif1":1->"msm_vfe0_rdi1":0[1]'
1. sudo media-ctl -d /dev/media0 -V '"mt9034 5-003a":0[fmt:UYVY2X8/1280x720],"msm_csiphy2":0[fmt:UYVY2X8/1280x720],"msm_csid1":0[fmt:UYVY2X8/1280x720],"msm_ispif1":0[fmt:UYVY2X8/1280x720],"msm_vfe0_rdi1":0[fmt:UYVY2X8/1280x720]'
1. sudo v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat='UYVY' -d /dev/video1
1. v4l2-ctl --stream-mmap=4 --verbose -d /dev/video1
1. polling_ms is in this file - drivers/gpu/drm/msm/msm_gpu_devfreq.c:90: .polling_ms = 50,
If #3 does not work for you, then let me know and I will proceed with getting access to our kernel repository.
Thanks, Kim
From: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:20 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
Sarah just let me know that the package may be stuck in customs, or something along those lines.
Dmitry, do you have any visibility about this from your end?
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com/
From: Kim Steiner kim.steiner@sightlineapplications.com Sent: Friday, February 03, 2023 2:06 PM To: Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Did you receive the new hd-sdi camera? Are you able to get video?
Have you looked into how to use a single GPU frequency in the 5.15 kernel?
Thanks, Kim
From: Kim Steiner Sent: Wednesday, January 25, 2023 12:02 PM To: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
1. I put a 5.15 kernel 4000 installer here: https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0 2. Our device tree sources, you can find here: https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0 3. I'm not 100% on what you will need if you use your 5.15 kernel build and want to run media-ctl and v4l2-ctl tools from the command line. What works for me is to
A. Run our VTNext_ARM64_Release.out - this is doing some FPGA reset and setup of GPIOs
B. sudo media-ctl -d /dev/media0 -l '"msm_csiphy2":1->"msm_csid1":0[1],"msm_csid1":1->"msm_ispif1":0[1],"msm_ispif1":1->"msm_vfe0_rdi1":0[1]'
1. sudo media-ctl -d /dev/media0 -V '"mt9034 5-003a":0[fmt:UYVY2X8/1280x720],"msm_csiphy2":0[fmt:UYVY2X8/1280x720],"msm_csid1":0[fmt:UYVY2X8/1280x720],"msm_ispif1":0[fmt:UYVY2X8/1280x720],"msm_vfe0_rdi1":0[fmt:UYVY2X8/1280x720]'
1. sudo v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat='UYVY' -d /dev/video1
1. v4l2-ctl --stream-mmap=4 --verbose -d /dev/video1
1. polling_ms is in this file - drivers/gpu/drm/msm/msm_gpu_devfreq.c:90: .polling_ms = 50,
If #3 does not work for you, then let me know and I will proceed with getting access to our kernel repository.
Thanks, Kim
From: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:20 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is "being held for review".
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is: 5711 S Hood Ave., Suite A Portland, OR 97239
From: Jordan Holt Sent: Wednesday, January 25, 2023 10:18 AM To: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to System then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.commailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.comhttp://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.orgmailto:sightlineapplications-leave@lists.linaro.org
Hello Steve,
On 04/02/2023 00:40, Steve Olson wrote:
Sarah just let me know that the package may be stuck in customs, or something along those lines.
Dmitry, do you have any visibility about this from your end?
I have been on a sick leave for two days, excuse me for not responding earlier.
I have sent an email to UPS support, hoping they provide additional information to me on what is required and what are the further steps with the parcel.
Thanks,
Steve
*Steve Olson | **CEO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him**
503 975-8478 (mobile) *| *www.sightlineapplications.com http://www.sightlineapplications.com/
*From:* Kim Steiner kim.steiner@sightlineapplications.com *Sent:* Friday, February 03, 2023 2:06 PM *To:* Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org *Cc:* Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
Did you receive the new hd-sdi camera? Are you able to get video?
Have you looked into how to use a single GPU frequency in the 5.15 kernel?
Thanks,
Kim
*From:* Kim Steiner *Sent:* Wednesday, January 25, 2023 12:02 PM *To:* Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
- I put a 5.15 kernel 4000 installer here: https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0 https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0
- Our device tree sources, you can find here: https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0 https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0
- I’m not 100% on what you will need if you use your 5.15 kernel build and want to run media-ctl and v4l2-ctl tools from the command line. What works for me is to
A. Run our VTNext_ARM64_Release.out – this is doing some FPGA reset and setup of GPIOs
B. sudo media-ctl -d /dev/media0 -l '"msm_csiphy2":1->"msm_csid1":0[1],"msm_csid1":1->"msm_ispif1":0[1],"msm_ispif1":1->"msm_vfe0_rdi1":0[1]'
sudo media-ctl -d /dev/media0 -V '"mt9034 5-003a":0[fmt:UYVY2X8/1280x720],"msm_csiphy2":0[fmt:UYVY2X8/1280x720],"msm_csid1":0[fmt:UYVY2X8/1280x720],"msm_ispif1":0[fmt:UYVY2X8/1280x720],"msm_vfe0_rdi1":0[fmt:UYVY2X8/1280x720]'
sudo v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat='UYVY' -d /dev/video1
v4l2-ctl --stream-mmap=4 --verbose -d /dev/video1
polling_ms is in this file - drivers/gpu/drm/msm/msm_gpu_devfreq.c:90: .polling_ms = 50,
If #3 does not work for you, then let me know and I will proceed with getting access to our kernel repository.
Thanks,
Kim
*From:* Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com> *Sent:* Wednesday, January 25, 2023 10:20 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is “being held for review”.
*Jordan Holt | **CTO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him | 503 724-9727**
Please note our *NEW PORTLAND ADDRESS* is:
/5711 S Hood Ave., Suite A/
/Portland, OR 97239/
*From:* Jordan Holt *Sent:* Wednesday, January 25, 2023 10:18 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to *System* then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.com http://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to
try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org
mailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com
mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>;
sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our
custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible
opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org mailto:sightlineapplications-leave@lists.linaro.org
Hi Kim,
I was on a sick leave, please excuse the delayed response.
On 04/02/2023 00:06, Kim Steiner wrote:
Hi Dmitry,
Did you receive the new hd-sdi camera? Are you able to get video?
No, not yet. The parcel is stuck.
Have you looked into how to use a single GPU frequency in the 5.15 kernel?
The frequencies for the GPU are handled both by the kernel and by the GPMU, a separate IP core. I'm debugging the way the kernel interacts with the GPMU.
Thanks,
Kim
*From:* Kim Steiner *Sent:* Wednesday, January 25, 2023 12:02 PM *To:* Jordan Holt jordan.holt@sightlineapplications.com; Steve Olson steve.olson@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org *Cc:* Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
- I put a 5.15 kernel 4000 installer here: https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0 https://www.dropbox.com/s/aktq45ybqty1640/SLAUpgrade4000.msi?dl=0
- Our device tree sources, you can find here: https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0 https://www.dropbox.com/s/gevgqyu79mtqy14/linaro_5.15_files.zip?dl=0
- I’m not 100% on what you will need if you use your 5.15 kernel build and want to run media-ctl and v4l2-ctl tools from the command line. What works for me is to
A. Run our VTNext_ARM64_Release.out – this is doing some FPGA reset and setup of GPIOs
B. sudo media-ctl -d /dev/media0 -l '"msm_csiphy2":1->"msm_csid1":0[1],"msm_csid1":1->"msm_ispif1":0[1],"msm_ispif1":1->"msm_vfe0_rdi1":0[1]'
sudo media-ctl -d /dev/media0 -V '"mt9034 5-003a":0[fmt:UYVY2X8/1280x720],"msm_csiphy2":0[fmt:UYVY2X8/1280x720],"msm_csid1":0[fmt:UYVY2X8/1280x720],"msm_ispif1":0[fmt:UYVY2X8/1280x720],"msm_vfe0_rdi1":0[fmt:UYVY2X8/1280x720]'
sudo v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat='UYVY' -d /dev/video1
v4l2-ctl --stream-mmap=4 --verbose -d /dev/video1
polling_ms is in this file - drivers/gpu/drm/msm/msm_gpu_devfreq.c:90: .polling_ms = 50,
If #3 does not work for you, then let me know and I will proceed with getting access to our kernel repository.
Thanks,
Kim
*From:* Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com> *Sent:* Wednesday, January 25, 2023 10:20 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
I tried to send with a picture, but mail is “being held for review”.
*Jordan Holt | **CTO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him | 503 724-9727**
Please note our *NEW PORTLAND ADDRESS* is:
/5711 S Hood Ave., Suite A/
/Portland, OR 97239/
*From:* Jordan Holt *Sent:* Wednesday, January 25, 2023 10:18 AM *To:* Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com>; Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> *Cc:* Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org *Subject:* RE: [Sightlineapplications] Re: Project Status and Burn Report
This should be the settings. If you can get it to display on your analog TV, click the middle button (press in) then toggle it up/down to get to *System* then press in then you want Frame Rate and Freq like below.
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Please note our NEW PORTLAND ADDRESS is:
5711 S Hood Ave., Suite A
Portland, OR 97239
-----Original Message----- From: Steve Olson <steve.olson@sightlineapplications.com mailto:steve.olson@sightlineapplications.com> Sent: Wednesday, January 25, 2023 10:14 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com> Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Yes, it's just NTSC composite video. I think can configure for PAL too, but to do that you need to be able to see the video to do that.
In parallel, I've started the process of sending you another camera and board.
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him
503 975-8478 (mobile) | www.sightlineapplications.com http://www.sightlineapplications.com
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org mailto:dmitry.baryshkov@linaro.org>
Sent: Wednesday, January 25, 2023 9:50 AM
To: Kim Steiner <kim.steiner@sightlineapplications.com mailto:kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: [Sightlineapplications] Re: Project Status and Burn Report
On 25/01/2023 19:47, Kim Steiner wrote:
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to
try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
I'll check if I can find a capture device. Is it just a composite video signal or something more intelligent?
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Tuesday, January 24, 2023 3:31 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org
mailto:dmitry.baryshkov@linaro.org>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com
mailto:jordan.holt@sightlineapplications.com>; Paul Neuhardt
<paul.neuhardt@linaro.org mailto:paul.neuhardt@linaro.org>;
sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn
Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our
custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible
opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
[ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000
[ 156.699833] rb 0: fence: 24134/24135
[ 156.717750] rptr: 6081
[ 156.721300] rb wptr: 6118
[ 156.724047] rb 1: fence: 0/0
[ 156.726786] rptr: 0
[ 156.729795] rb wptr: 0
[ 156.732207] rb 2: fence: 0/0
[ 156.734670] rptr: 0
[ 156.737779] rb wptr: 0
[ 156.740191] rb 3: fence: 0/0
[ 156.742649] rptr: 0
[ 156.745768] rb wptr: 0
[ 156.748186] CP_SCRATCH_REG0: 0
[ 156.750641] CP_SCRATCH_REG1: 0
[ 156.753762] CP_SCRATCH_REG2: 24134
[ 156.756812] CP_SCRATCH_REG3: 0
[ 156.760169] CP_SCRATCH_REG4: 0
[ 156.763222] CP_SCRATCH_REG5: 0
[ 156.766262] CP_SCRATCH_REG6: 0
[ 156.769300] CP_SCRATCH_REG7: 0
[ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530:
hangcheck recover!
Thanks,
Kim
--
With best wishes
Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org mailto:sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org mailto:sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
I tried a full recovery to 4.14 on the SLA-4000. Then flashed the latest 5.15 kernel and modules to the board. The board boots just fine. Something must have gotten changed since earlier testing of 5.15 😊
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Wednesday, January 25, 2023 9:48 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
Hi Kim,
On 08/02/2023 22:42, Kim Steiner wrote:
Hi Dmitry,
I tried a full recovery to 4.14 on the SLA-4000. Then flashed the latest 5.15 kernel and modules to the board. The board boots just fine. Something must have gotten changed since earlier testing of 5.15 😊
Thanks for the confirmation!
We had a debugging session with Tamotsu-san. He assisted me with the license file and checking of the boards, but we still were not able to enable the HD-SDI camera (switching to the replaced HD-SDI board and camera). I have provided him with the logs of the Sightline software service. Hopefully we can solve the HD-SDI camera issue at some point.
Regarding the load testing.
Could you please compare the following items between 4.14 and 5.15:
- cat /proc/loadavg (this is the load average of the CPUs)
- sudo cat /sys/kernel/debug/dri/0/perf (this outpus current load of the GPU)
- measure the actual frequencies of the CPU clusters:
git clone https://github.com/andersson/debugcc.git cd debugcc make sudo ./msm8996-debugcc -p msm8996 -a -b cpu
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Wednesday, January 25, 2023 9:48 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
Hi Dmitry,
Attached are the results. Also, I did a little more testing with recovery and then loading 5.15 kernel+modules. I noticed that 5.15 boots but it hangs here:
Starting Terminate Plymouth Boot Screen... Starting Hold until boot process finishes up...
And I never am able to type in the serial debug window. I can SSH into the board fine though.
Also, I noticed this error today when running 5.15 kernel (getting results of tests):
root@sla-alip:~# sudo cat /proc/loadavg 1.16 0.84 0.49 3/199 1345 root@sla-alip:~# [ 410.704947] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) õSÀ[ 411.067140] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) øþ¿ÿÿÿÿ.WÿÖ[ 412.458001] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) [ 412.476099] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unm[ 412.568713] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) rmynate/allátas(e) memory/full-oíï[[ÿ·f) kill_[K]?.¥ZJHº´aw-filesystems(n) sak(k) show [ 412.584889] sysrq: Emergency Sync [ 412.611825] Emergency Sync complete
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, February 8, 2023 3:32 PM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 08/02/2023 22:42, Kim Steiner wrote:
Hi Dmitry,
I tried a full recovery to 4.14 on the SLA-4000. Then flashed the latest 5.15 kernel and modules to the board. The board boots just fine. Something must have gotten changed since earlier testing of 5.15 😊
Thanks for the confirmation!
We had a debugging session with Tamotsu-san. He assisted me with the license file and checking of the boards, but we still were not able to enable the HD-SDI camera (switching to the replaced HD-SDI board and camera). I have provided him with the logs of the Sightline software service. Hopefully we can solve the HD-SDI camera issue at some point.
Regarding the load testing.
Could you please compare the following items between 4.14 and 5.15:
- cat /proc/loadavg (this is the load average of the CPUs)
- sudo cat /sys/kernel/debug/dri/0/perf (this outpus current load of the GPU)
- measure the actual frequencies of the CPU clusters:
git clone https://github.com/andersson/debugcc.git cd debugcc make sudo ./msm8996-debugcc -p msm8996 -a -b cpu
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Wednesday, January 25, 2023 9:48 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Hi Dmitry,
One other thought in terms of getting the hd-sdi camera to work is to try the analog out connector. It is the yellow connector on the hd-sdi camera cabling. Would you have a way to display this?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Tuesday, January 24, 2023 3:31 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Resending with basically no message then this one:
Hi Dmitry,
In regards to our testing, we have seen a GPU fault crash with our custom board (with 5.15 kernel) during temp testing. On one unit, we have seen the GPU fault crash at 118F (47C) while our custom board is sitting on a desk. The output of the GPU fault crash occurs once and our application continues to run. What do you think of this output?:
[ 156.660355] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 156.662139] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.666297] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 156.680832] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 156.699196] revision: 530 (5.3.0.2) [ 156.699341] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 5e47 status 800001C1 rb 1820/17e6 ib1 0000000003C1B000/0000 ib2 0000000001483000/0000 [ 156.699833] rb 0: fence: 24134/24135 [ 156.717750] rptr: 6081 [ 156.721300] rb wptr: 6118 [ 156.724047] rb 1: fence: 0/0 [ 156.726786] rptr: 0 [ 156.729795] rb wptr: 0 [ 156.732207] rb 2: fence: 0/0 [ 156.734670] rptr: 0 [ 156.737779] rb wptr: 0 [ 156.740191] rb 3: fence: 0/0 [ 156.742649] rptr: 0 [ 156.745768] rb wptr: 0 [ 156.748186] CP_SCRATCH_REG0: 0 [ 156.750641] CP_SCRATCH_REG1: 0 [ 156.753762] CP_SCRATCH_REG2: 24134 [ 156.756812] CP_SCRATCH_REG3: 0 [ 156.760169] CP_SCRATCH_REG4: 0 [ 156.763222] CP_SCRATCH_REG5: 0 [ 156.766262] CP_SCRATCH_REG6: 0 [ 156.769300] CP_SCRATCH_REG7: 0 [ 156.773675] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover!
Thanks, Kim
-- With best wishes Dmitry
Hi Dmitry, I am running the 4000 as follows to cause the GPU hang bug:
1. Board in a freezer - ours isn't super controllable, but a thermometer says it is at -18C. 2. Set up so that you can cycle the board power - needed when you hit the crash 3. I have a small fan in the freezer pointed at the board with a power cord coming out so that I can turn it on and off. 4. Default parameters on the 4000 except * Cam 0 is set up with TestPattern Multi Car, 1080x1920, color * Stream network video to your PC * Parameters -> Save To Board 5. View Performance Graphs, check Enable System Status and look at the Temperature value (see below) 6. Try to get the temperature into the high 50'sF to low 60'sF (sorry it's F instead of C!) and you will see: Warning: GPU hang detected ... messages and jumpy video. * Turn on the fan if the temperature is too high (usually not for very long) * You can try turning on other processing temporarily if the temperature is too low, then turn these off once it warms up.
i. Enhance -> Contrast Mode = CLAHE
ii. Track -> Detect -> Mode = Aerial
1. Occasionally, the whole system will crash, requires a power cycle 2. Let's get on a call if you are struggling to get it into the zone.
[cid:image001.png@01D9484E.381BB850]
Thanks, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Hi Dmitry,
Are you having any success with setting up a freezer to reproduce the GPU hang bug?
Also, are you able to get us a patch for a single GPU frequency in the latest code base?
Thanks, Kim
From: Jordan Holt jordan.holt@sightlineapplications.com Sent: Friday, February 24, 2023 1:15 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Low temperature GPU hang testing
Hi Dmitry, I am running the 4000 as follows to cause the GPU hang bug:
1. Board in a freezer - ours isn't super controllable, but a thermometer says it is at -18C. 2. Set up so that you can cycle the board power - needed when you hit the crash 3. I have a small fan in the freezer pointed at the board with a power cord coming out so that I can turn it on and off. 4. Default parameters on the 4000 except * Cam 0 is set up with TestPattern Multi Car, 1080x1920, color * Stream network video to your PC * Parameters -> Save To Board 5. View Performance Graphs, check Enable System Status and look at the Temperature value (see below) 6. Try to get the temperature into the high 50'sF to low 60'sF (sorry it's F instead of C!) and you will see: Warning: GPU hang detected ... messages and jumpy video. * Turn on the fan if the temperature is too high (usually not for very long) * You can try turning on other processing temporarily if the temperature is too low, then turn these off once it warms up.
i. Enhance -> Contrast Mode = CLAHE
ii. Track -> Detect -> Mode = Aerial
1. Occasionally, the whole system will crash, requires a power cycle 2. Let's get on a call if you are struggling to get it into the zone.
[cid:image001.png@01D94D96.95A5E250]
Thanks, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Forgot to mention that if you need help setting up the freezer or reproducing the issue, we are happy to set up a teams meeting to help. Thanks, Kim
From: Kim Steiner Sent: Friday, March 3, 2023 6:09 AM To: Jordan Holt jordan.holt@sightlineapplications.com; Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
Are you having any success with setting up a freezer to reproduce the GPU hang bug?
Also, are you able to get us a patch for a single GPU frequency in the latest code base?
Thanks, Kim
From: Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Sent: Friday, February 24, 2023 1:15 PM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Low temperature GPU hang testing
Hi Dmitry, I am running the 4000 as follows to cause the GPU hang bug:
1. Board in a freezer - ours isn't super controllable, but a thermometer says it is at -18C. 2. Set up so that you can cycle the board power - needed when you hit the crash 3. I have a small fan in the freezer pointed at the board with a power cord coming out so that I can turn it on and off. 4. Default parameters on the 4000 except * Cam 0 is set up with TestPattern Multi Car, 1080x1920, color * Stream network video to your PC * Parameters -> Save To Board 5. View Performance Graphs, check Enable System Status and look at the Temperature value (see below) 6. Try to get the temperature into the high 50'sF to low 60'sF (sorry it's F instead of C!) and you will see: Warning: GPU hang detected ... messages and jumpy video. * Turn on the fan if the temperature is too high (usually not for very long) * You can try turning on other processing temporarily if the temperature is too low, then turn these off once it warms up.
i. Enhance -> Contrast Mode = CLAHE
ii. Track -> Detect -> Mode = Aerial
1. Occasionally, the whole system will crash, requires a power cycle 2. Let's get on a call if you are struggling to get it into the zone.
[cid:image001.png@01D94D96.C0FAB7F0]
Thanks, Jordan
Jordan Holt | CTO | SightLine Applications Inc. | Onboard Video Processing | he/him | 503 724-9727
Hi Kim,
On 03/03/2023 16:08, Kim Steiner wrote:
Hi Dmitry,
Are you having any success with setting up a freezer to reproduce the GPU hang bug?
I had a partial success, I was able to once reproduce an issue with my setup. I pushed several patches fixing small GPU issues, fixing the devfreq/scaling frequency and also changing the way GPU handles the MX power rail. Also I pushed several patches that would trigger GPU to use higher frequencies/higher power consumption if exposed to the lower temperatures. I'm currently evaluating if it is possible to slightly increase voltage under the low-temp conditions.
The changes have now propagated to the old Git server, so you can pull them from the old location.
Also, are you able to get us a patch for a single GPU frequency in the latest code base?
I have attached a patch that limits the frequencies to 560MHz and 624 MHz, as those two frequencies are supported by most of msm8996 SoCs. If your device supports 624 MHz for the GPU, you also disable the 560 MHz opp entry. Note, this patch overrides some of voltage controls and thus can occasionally lead to crashes.
Could you please perform: - a performance test of the new kernel - a performance test of the new kernel with the patch applied?
Thanks,
Kim
*From:* Jordan Holt jordan.holt@sightlineapplications.com *Sent:* Friday, February 24, 2023 1:15 PM *To:* Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com *Cc:* Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org *Subject:* Low temperature GPU hang testing
Hi Dmitry,
I am running the 4000 as follows to cause the GPU hang bug:
- Board in a freezer – ours isn’t super controllable, but a thermometer says it is at -18C.
- Set up so that you can cycle the board power – needed when you hit the crash
- I have a small fan in the freezer pointed at the board with a power cord coming out so that I can turn it on and off.
- Default parameters on the 4000 except
- Cam 0 is set up with TestPattern Multi Car, 1080x1920, color
- Stream network video to your PC
- Parameters -> Save To Board
- View Performance Graphs, check Enable System Status and look at the Temperature value (see below)
- Try to get the temperature into the high 50’sF to low 60’sF (sorry it’s F instead of C!) and you will see: *Warning: GPU hang detected …* messages and jumpy video.
- Turn on the fan if the temperature is too high (usually not for very long)
- You can try turning on other processing temporarily if the temperature is too low, then turn these off once it warms up.
i.Enhance -> Contrast Mode = CLAHE
ii.Track -> Detect -> Mode = Aerial
- Occasionally, the whole system will crash, requires a power cycle
- Let’s get on a call if you are struggling to get it into the zone.
Thanks,
Jordan
*Jordan Holt | **CTO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him | 503 724-9727**
Hi Dmitry,
Here is the log of our boot up with the 2 frequencies patch.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, March 6, 2023 4:55 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 03/03/2023 16:08, Kim Steiner wrote:
Hi Dmitry,
Are you having any success with setting up a freezer to reproduce the GPU hang bug?
I had a partial success, I was able to once reproduce an issue with my setup. I pushed several patches fixing small GPU issues, fixing the devfreq/scaling frequency and also changing the way GPU handles the MX power rail. Also I pushed several patches that would trigger GPU to use higher frequencies/higher power consumption if exposed to the lower temperatures. I'm currently evaluating if it is possible to slightly increase voltage under the low-temp conditions.
The changes have now propagated to the old Git server, so you can pull them from the old location.
Also, are you able to get us a patch for a single GPU frequency in the latest code base?
I have attached a patch that limits the frequencies to 560MHz and 624 MHz, as those two frequencies are supported by most of msm8996 SoCs. If your device supports 624 MHz for the GPU, you also disable the 560 MHz opp entry. Note, this patch overrides some of voltage controls and thus can occasionally lead to crashes.
Could you please perform: - a performance test of the new kernel - a performance test of the new kernel with the patch applied?
Thanks,
Kim
*From:* Jordan Holt jordan.holt@sightlineapplications.com *Sent:* Friday, February 24, 2023 1:15 PM *To:* Dmitry Baryshkov dmitry.baryshkov@linaro.org; Kim Steiner kim.steiner@sightlineapplications.com *Cc:* Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org *Subject:* Low temperature GPU hang testing
Hi Dmitry,
I am running the 4000 as follows to cause the GPU hang bug:
- Board in a freezer – ours isn’t super controllable, but a thermometer says it is at -18C.
- Set up so that you can cycle the board power – needed when you hit the crash
- I have a small fan in the freezer pointed at the board with a power cord coming out so that I can turn it on and off.
- Default parameters on the 4000 except
- Cam 0 is set up with TestPattern Multi Car, 1080x1920, color
- Stream network video to your PC
- Parameters -> Save To Board
- View Performance Graphs, check Enable System Status and look at the Temperature value (see below)
- Try to get the temperature into the high 50’sF to low 60’sF (sorry it’s F instead of C!) and you will see: *Warning: GPU hang detected …* messages and jumpy video.
- Turn on the fan if the temperature is too high (usually not for very long)
- You can try turning on other processing temporarily if the temperature is too low, then turn these off once it warms up.
i.Enhance -> Contrast Mode = CLAHE
ii.Track -> Detect -> Mode = Aerial
- Occasionally, the whole system will crash, requires a power cycle
- Let’s get on a call if you are struggling to get it into the zone.
Thanks,
Jordan
*Jordan Holt | **CTO **| SightLine Applications Inc. |**Onboard Video**Processing****| *he/him | 503 724-9727**
-- With best wishes Dmitry
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
Hi Kim,
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
No updates from my side for now, I have been looking for the possible causes of the reset you have reported last time. Yes, I'm using a kernel from your repo, thank you.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/ SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
Hi Dmitry,
Anything new for us to test? Are you still working on a single GPU frequency patch for us?
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 23, 2023 12:42 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/ SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
Hi Kim
On 30/03/2023 19:40, Kim Steiner wrote:
Hi Dmitry,
Please excuse me for not responding earlier. Somehow this email got into a different folder and thus I missed it. Please accept my humble apologies.
Anything new for us to test? Are you still working on a single GPU frequency patch for us?
Maybe there was some kind of misunderstanding. Does this last patch I have sent you fix the issue on two boards that were resetting with the previous single-frequency patch? Which speed bin do they report (look for the "Detected speed bin" kernel log entry.
From the software perspective point of view the freq.patch I have send you in the last email should be as good as a the single-freq: it powers on the GPU and then switches to the highest possible frequency, taking into account GPU speed classification, possible overheating, etc. It user the performance governor, so it will not lower the frequency unless required by the CPU/GPU being close to the melting point.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 23, 2023 12:42 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com/ SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
Hi Dmitry,
As I stated below, what I observed with the two patches were these kernel messages, which did not seem like it was setting a single GPU frequency (133MHz, 315MHz and 624MHz):
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Are you saying these frequencies are not getting set? Maybe the patches got mixed up? Can you create a patch from our repo since you have access? Then I can try that patch?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 5:07 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 30/03/2023 19:40, Kim Steiner wrote:
Hi Dmitry,
Please excuse me for not responding earlier. Somehow this email got into a different folder and thus I missed it. Please accept my humble apologies.
Anything new for us to test? Are you still working on a single GPU frequency patch for us?
Maybe there was some kind of misunderstanding. Does this last patch I have sent you fix the issue on two boards that were resetting with the previous single-frequency patch? Which speed bin do they report (look for the "Detected speed bin" kernel log entry.
From the software perspective point of view the freq.patch I have send you in the last email should be as good as a the single-freq: it powers on the GPU and then switches to the highest possible frequency, taking into account GPU speed classification, possible overheating, etc. It user the performance governor, so it will not lower the frequency unless required by the CPU/GPU being close to the melting point.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 23, 2023 12:42 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com / SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim
ср, 5 апр. 2023 г., 16:12 Kim Steiner <kim.steiner@sightlineapplications.com
:
Hi Dmitry,
As I stated below, what I observed with the two patches were these kernel messages, which did not seem like it was setting a single GPU frequency (133MHz, 315MHz and 624MHz):
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't
have 20 1's, 20 0's
[ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed
(AKSV=6800000000)
[ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Did it report frequency changes after this line?
Are you saying these frequencies are not getting set? Maybe the patches got mixed up? Can you create a patch from our repo since you have access? Then I can try that patch?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 5:07 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt < jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 30/03/2023 19:40, Kim Steiner wrote:
Hi Dmitry,
Please excuse me for not responding earlier. Somehow this email got into a different folder and thus I missed it. Please accept my humble apologies.
Anything new for us to test? Are you still working on a single GPU
frequency patch for us?
Maybe there was some kind of misunderstanding. Does this last patch I have sent you fix the issue on two boards that were resetting with the previous single-frequency patch? Which speed bin do they report (look for the "Detected speed bin" kernel log entry.
From the software perspective point of view the freq.patch I have send you in the last email should be as good as a the single-freq: it powers on the GPU and then switches to the highest possible frequency, taking into account GPU speed classification, possible overheating, etc. It user the performance governor, so it will not lower the frequency unless required by the CPU/GPU being close to the melting point.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 23, 2023 12:42 PM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement
because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't
have 20 1's, 20 0's
[ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed
(AKSV=6800000000)
[ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you
try building the kernel from our repo?
After spending some time testing it locally, I still was not able to
reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org; Jordan Holt jordan.holt@sightlineapplications.com Cc: Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.com / SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Thanks, Kim
From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 6:34 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim ср, 5 апр. 2023 г., 16:12 Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>: Hi Dmitry,
As I stated below, what I observed with the two patches were these kernel messages, which did not seem like it was setting a single GPU frequency (133MHz, 315MHz and 624MHz):
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Did it report frequency changes after this line?
Are you saying these frequencies are not getting set? Maybe the patches got mixed up? Can you create a patch from our repo since you have access? Then I can try that patch?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Wednesday, April 5, 2023 5:07 AM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 30/03/2023 19:40, Kim Steiner wrote:
Hi Dmitry,
Please excuse me for not responding earlier. Somehow this email got into a different folder and thus I missed it. Please accept my humble apologies.
Anything new for us to test? Are you still working on a single GPU frequency patch for us?
Maybe there was some kind of misunderstanding. Does this last patch I have sent you fix the issue on two boards that were resetting with the previous single-frequency patch? Which speed bin do they report (look for the "Detected speed bin" kernel log entry.
From the software perspective point of view the freq.patch I have send you in the last email should be as good as a the single-freq: it powers on the GPU and then switches to the highest possible frequency, taking into account GPU speed classification, possible overheating, etc. It user the performance governor, so it will not lower the frequency unless required by the CPU/GPU being close to the melting point.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 23, 2023 12:42 PM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I tested the combined patch (I had to change the dev_info statement because I got a build error) and the board appears to boot ok.
I see some messages print: [ 34.745966] adreno b00000.gpu: GPU setting to 133000000 [ 34.754545] msm_hdmi_hdcp_read_validate_aksv: AKSV QFPROM doesn't have 20 1's, 20 0's [ 34.754630] msm_hdmi_hdcp_read_validate_aksv: QFPROM AKSV chk failed (AKSV=6800000000) [ 34.761428] [drm:mdp5_irq_error_handler] *ERROR* errors: 40000000 [ 34.769257] msm_hdmi_hdcp_auth_prepare: ASKV validation failed [ 34.775762] msm_hdmi_hdcp_auth_work: auth prepare failed -524 [ 34.781566] msm_hdmi_hdcp_auth_work: hdcp is not supported [ 34.998064] adreno b00000.gpu: GPU setting to 315000000 [ 35.262050] adreno b00000.gpu: GPU setting to 624000000
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org> Sent: Tuesday, March 21, 2023 9:38 AM To: Kim Steiner <kim.steiner@sightlineapplications.commailto:kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim
On 15/03/2023 00:13, Kim Steiner wrote:
Hi Dmitry,
Anything new to report on your end? Anything for us to test? Did you try building the kernel from our repo?
After spending some time testing it locally, I still was not able to reproduce the latest issue you have reported (some of the boards rebooting with the single-frequency patch). Could you please test the attached patch on top of the single-freq patch? I would be very interested in the dmesg output both if the attached patch fixes the issue on your side and if it does not.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, March 9, 2023 7:57 AM To: Dmitry Baryshkov <dmitry.baryshkov@linaro.orgmailto:dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.commailto:jordan.holt@sightlineapplications.com> Cc: Paul Neuhardt <paul.neuhardt@linaro.orgmailto:paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.orgmailto:sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
I added you to the 5.15Linarokrn repository.
git clone https://<username>%40sightlineapplications.com@git7.projectlocker.commailto:40sightlineapplications.com@git7.projectlocker.com / SightLineApplications/5.15Linarokrn.git
The username should be the same as for the 4.14 kernel login.
Thanks, Kim
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in: - speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg: [ 4.105174] adreno b00000.gpu: Detected speed bin 0
- checking that GPU performance matches the expectations.
- checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktEXY6eYp...
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in: - speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg: [ 4.105174] adreno b00000.gpu: Detected speed bin 0
- checking that GPU performance matches the expectations.
- checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
Forgot to mention that the GPU is also slower. You can observe that in the link below.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Thursday, April 6, 2023 10:56 AM To: 'Dmitry Baryshkov' dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: Low temperature GPU hang testing
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktEXY6eYp...
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in: - speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg: [ 4.105174] adreno b00000.gpu: Detected speed bin 0
- checking that GPU performance matches the expectations.
- checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktEXY6eYp...
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
Hi Dmitry,
This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Can you try the link again? I changed permissions.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry,
This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Ack, thanks
Can you try the link again? I changed permissions.
Yes, it works now.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
Dmitry, did you get the board from lantronix yet?
Thanks,
Steve
On Apr 6, 2023, at 11:54 AM, Dmitry Baryshkov dmitry.baryshkov@linaro.org wrote:
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry, This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Ack, thanks
Can you try the link again? I changed permissions.
Yes, it works now.
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote: Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following: [ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22 So, some parts of the board might be underpowered. I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Steve,
On 07/04/2023 04:49, Steve Olson wrote:
Dmitry, did you get the board from lantronix yet?
No, I did not receive it yet. Here is a transcript with the chat with support person:
Krzysztof H (06/04/2023, 15:04:35): okay, as I see package was sent to lockerbox at 2nd of April Krzysztof H (06/04/2023, 15:04:46): to be honest it should be already in lockerbox at 5th of April Krzysztof H (06/04/2023, 15:04:58): you didn't recieved any sms with location and code? Me (06/04/2023, 15:05:11): No Me (06/04/2023, 15:05:57): And the tracking page visible to me shows: Me (06/04/2023, 15:05:58): Friday, 31/03/2023 Delay Rerouted to revised delivery address Krzysztof H (06/04/2023, 15:06:23): but rerouted wasn't possible due of wrong phone number Krzysztof H (06/04/2023, 15:06:33): correct phone number was provided for us at 02.04 Me (06/04/2023, 15:07:39): Hmm. How is that possible? I had a missed call and an SMS from FedEx on Friday, 31.03 Krzysztof H (06/04/2023, 15:07:44): I think sender made mistake, so they send us correct phone number at the beginning of this week Krzysztof H (06/04/2023, 15:08:18): becouse simply it depends on what sender procided, in fedex system are two tabs for number, one at package, second one is for notifications Krzysztof H (06/04/2023, 15:08:29): I think sender just provided two different numbers Me (06/04/2023, 15:08:37): +358 469526397 Krzysztof H (06/04/2023, 15:08:44): that was phone number provided firstly "5037249727" Me (06/04/2023, 15:09:04): Yes. That is my phone and I was contacted on this phone on Friday. Me (06/04/2023, 15:09:32): ok. Anyway, how can we resolve this situation? Krzysztof H (06/04/2023, 15:10:51): well, I will ask our colleagues from support team to reach lockerbox company and to push your package. I will also tell them to send notification about location at this number +358 469526397, okay? Me (06/04/2023, 15:11:05): Yes, this is fine. Thank you
Thanks,
Steve
On Apr 6, 2023, at 11:54 AM, Dmitry Baryshkov dmitry.baryshkov@linaro.org wrote:
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry, This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Ack, thanks
Can you try the link again? I changed permissions.
Yes, it works now.
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote: Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following: [ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22 So, some parts of the board might be underpowered. I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Kim,
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry,
This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Just to verify: does this board work with 4.14?
Can you try the link again? I changed permissions.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
Hi Dmitry, Yes, this board works with 4.14 kernel.
Also, we can get the second 4000-OEM to crash when running our software if we power off the unit for a while (an hour) and then power the 4000-OEM back on. Attached is the failure log for this second unit. This board also runs 4.14 kernel successfully.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, April 7, 2023 8:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim,
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry,
This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Just to verify: does this board work with 4.14?
Can you try the link again? I changed permissions.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxkt E XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
Here is a successful run of the second 4000-OEM. This can provide some clue. To get our software to load and run, I had to leave the unit powered on (warm up), then I power cycled and our software runs ok.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Friday, April 7, 2023 8:38 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry, Yes, this board works with 4.14 kernel.
Also, we can get the second 4000-OEM to crash when running our software if we power off the unit for a while (an hour) and then power the 4000-OEM back on. Attached is the failure log for this second unit. This board also runs 4.14 kernel successfully.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, April 7, 2023 8:15 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim,
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry,
This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Just to verify: does this board work with 4.14?
Can you try the link again? I changed permissions.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote:
Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following:
[ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22
So, some parts of the board might be underpowered.
I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxkt E XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
_______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Yikes! What a nightmare.
We're still working with Lantronix to get you documentation in case you need it in the future. Unfortunately, We don't think we can help with the crazy lockbox situation -- I hope it is resolved soon!
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com Visit us at XPONENTIAL | May 9 – 11, 2023 | Booth #3627
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, April 07, 2023 6:03 AM To: Steve Olson steve.olson@sightlineapplications.com Cc: Kim Steiner kim.steiner@sightlineapplications.com; Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Steve,
On 07/04/2023 04:49, Steve Olson wrote:
Dmitry, did you get the board from lantronix yet?
No, I did not receive it yet. Here is a transcript with the chat with support person:
Krzysztof H (06/04/2023, 15:04:35): okay, as I see package was sent to lockerbox at 2nd of April Krzysztof H (06/04/2023, 15:04:46): to be honest it should be already in lockerbox at 5th of April Krzysztof H (06/04/2023, 15:04:58): you didn't recieved any sms with location and code? Me (06/04/2023, 15:05:11): No Me (06/04/2023, 15:05:57): And the tracking page visible to me shows: Me (06/04/2023, 15:05:58): Friday, 31/03/2023 Delay Rerouted to revised delivery address Krzysztof H (06/04/2023, 15:06:23): but rerouted wasn't possible due of wrong phone number Krzysztof H (06/04/2023, 15:06:33): correct phone number was provided for us at 02.04 Me (06/04/2023, 15:07:39): Hmm. How is that possible? I had a missed call and an SMS from FedEx on Friday, 31.03 Krzysztof H (06/04/2023, 15:07:44): I think sender made mistake, so they send us correct phone number at the beginning of this week Krzysztof H (06/04/2023, 15:08:18): becouse simply it depends on what sender procided, in fedex system are two tabs for number, one at package, second one is for notifications Krzysztof H (06/04/2023, 15:08:29): I think sender just provided two different numbers Me (06/04/2023, 15:08:37): +358 469526397 Krzysztof H (06/04/2023, 15:08:44): that was phone number provided firstly "5037249727" Me (06/04/2023, 15:09:04): Yes. That is my phone and I was contacted on this phone on Friday. Me (06/04/2023, 15:09:32): ok. Anyway, how can we resolve this situation? Krzysztof H (06/04/2023, 15:10:51): well, I will ask our colleagues from support team to reach lockerbox company and to push your package. I will also tell them to send notification about location at this number +358 469526397, okay? Me (06/04/2023, 15:11:05): Yes, this is fine. Thank you
Thanks,
Steve
On Apr 6, 2023, at 11:54 AM, Dmitry Baryshkov dmitry.baryshkov@linaro.org wrote:
On 06/04/2023 21:51, Kim Steiner wrote:
Hi Dmitry, This is the parameter file from the board that is having issues. You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a single cam0 configured as a testpattern 1080p image.
Ack, thanks
Can you try the link again? I changed permissions.
Yes, it works now.
Thanks, Kim -----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Thursday, April 6, 2023 11:31 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
On 06/04/2023 20:56, Kim Steiner wrote: Hi Dmitry,
With the latest patch for 5.15, both boards that didn't boot up now boot, but one of the two boards crashes when we run our software. Attached is the dmesg log.
This is interesting. I also noticed the following: [ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.186515] qcom-camss a34000.camss: Failed to power up pipeline: -22 [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to power domain [ 44.199654] qcom-camss a34000.camss: Failed to power up pipeline: -22 So, some parts of the board might be underpowered. I will take a look, what can be causing this issue or how can we cope with that. In the mean time, could you please describe, which camera is enabled on this board?
With the latest patch for 5.15, we observe that the CPU functions (Analyze) is a little slower. We also observe that power usage has increased between 4.14 and 5.15: https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQx ktE XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
I don't have access to this document.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 5, 2023 10:57 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: Low temperature GPU hang testing
Hi Kim,
On 05/04/2023 17:08, Kim Steiner wrote:
Hi Dmitry,
This was two weeks ago when I ran this, but I do not think so. Although we didn’t do any temp test in our freezer (room temp only), because we didn’t hear back from you on if this was correct. Should we?
I think you should create a single patch for us to test because the last patch you sent us did not compile, so I’m wondering if the correct patch was sent to us. In that patch, this line didn’t compile: dev_info(gpu: "GPU setting to %ld\n", *freq);
Please give a series of tests to the attached patch. I'm interested in:
- speed bins for the boards that crashed when you tested the previous version, check the following line in the dmesg:
[ 4.105174] adreno b00000.gpu: Detected speed bin 0
checking that GPU performance matches the expectations.
checking that the boards are stable in normal conditions and in the fridge test.
Thank you for your testing!
-- With best wishes Dmitry
-- With best wishes Dmitry
-- With best wishes Dmitry
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
-- With best wishes Dmitry
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
Hi Dmitry,
I haven't heard back from you and am wondering if my emails are going into a junk email folder. Is there anything we can do on our end to help with testing? Please inform us.
I wanted to pass along our build script that we use and .config file that was recently created.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, April 10, 2023 10:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
Hi Kim,
On Wed, 12 Apr 2023 at 15:55, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
I haven't heard back from you and am wondering if my emails are going into a junk email folder. Is there anything we can do on our end to help with testing? Please inform us.
No, I got all your emails (and I started monitoring my Spam folder regularly, so I know that I got all of them). Friday and Monday were government holidays here. Other than that I was able to reproduce the cold-boot-failure, warm-boot-works issue here. I'm working on that, but since it is only a cold-boot issue, it takes time to test it.
I wanted to pass along our build script that we use and .config file that was recently created.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, April 10, 2023 10:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
Thanks for the update Dmitry. Let us know if you need us to test anything.
Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 12, 2023 6:06 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim,
On Wed, 12 Apr 2023 at 15:55, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
I haven't heard back from you and am wondering if my emails are going into a junk email folder. Is there anything we can do on our end to help with testing? Please inform us.
No, I got all your emails (and I started monitoring my Spam folder regularly, so I know that I got all of them). Friday and Monday were government holidays here. Other than that I was able to reproduce the cold-boot-failure, warm-boot-works issue here. I'm working on that, but since it is only a cold-boot issue, it takes time to test it.
I wanted to pass along our build script that we use and .config file that was recently created.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, April 10, 2023 10:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
-- With best wishes Dmitry
HI Dmitry and Paul,
On the call this morning (for us), Jordan and I tossed out a couple of ideas about porting changes to 4.14 and to generating alternative kernels without your power changes.
After discussing here, we'd like for you to ignore these ideas and keep working on tasks as you have been.
Our top priority is to get a functional 5.15 that survives cold boots ASAP.
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com Visit us at XPONENTIAL | May 9 - 11, 2023 | Booth #3627
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 12, 2023 6:06 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim,
On Wed, 12 Apr 2023 at 15:55, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
I haven't heard back from you and am wondering if my emails are going into a junk email folder. Is there anything we can do on our end to help with testing? Please inform us.
No, I got all your emails (and I started monitoring my Spam folder regularly, so I know that I got all of them). Friday and Monday were government holidays here. Other than that I was able to reproduce the cold-boot-failure, warm-boot-works issue here. I'm working on that, but since it is only a cold-boot issue, it takes time to test it.
I wanted to pass along our build script that we use and .config file that was recently created.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, April 10, 2023 10:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
On Wed, 19 Apr 2023 at 20:58, Steve Olson steve.olson@sightlineapplications.com wrote:
HI Dmitry and Paul,
On the call this morning (for us), Jordan and I tossed out a couple of ideas about porting changes to 4.14 and to generating alternative kernels without your power changes.
After discussing here, we'd like for you to ignore these ideas and keep working on tasks as you have been.
Our top priority is to get a functional 5.15 that survives cold boots ASAP.
Ack.
Thanks,
Steve
Steve Olson | CEO | SightLine Applications Inc. | Onboard Video Processing | he/him 503 975-8478 (mobile) | www.sightlineapplications.com Visit us at XPONENTIAL | May 9 - 11, 2023 | Booth #3627
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Wednesday, April 12, 2023 6:06 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim,
On Wed, 12 Apr 2023 at 15:55, Kim Steiner kim.steiner@sightlineapplications.com wrote:
Hi Dmitry,
I haven't heard back from you and am wondering if my emails are going into a junk email folder. Is there anything we can do on our end to help with testing? Please inform us.
No, I got all your emails (and I started monitoring my Spam folder regularly, so I know that I got all of them). Friday and Monday were government holidays here. Other than that I was able to reproduce the cold-boot-failure, warm-boot-works issue here. I'm working on that, but since it is only a cold-boot issue, it takes time to test it.
I wanted to pass along our build script that we use and .config file that was recently created.
Thanks, Kim
-----Original Message----- From: Kim Steiner Sent: Monday, April 10, 2023 10:57 AM To: Dmitry Baryshkov dmitry.baryshkov@linaro.org Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: RE: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Dmitry,
Noticed with the latest (when I can get our software to run), 1.) I get gpu hang detect messages
26.616113] adreno b00000.gpu: GPU setting to 624000000 [ 30.081844] random: crng init done [ 30.081935] random: 864 urandom warning(s) missed due to ratelimiting [ 624.052706] msm 900000.mdss: CP | opcode error | possible opcode=0x00000000 [ 624.054408] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.058658] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 624.085110] msm 900000.mdss: [drm:a5xx_irq] *ERROR* gpu fault ring 0 fence 13c06 status 800001C1 rb 0d70/0d11 ib1 0000000003C16000/0000 ib2 0000000001482000/0000 [ 624.085265] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.829113] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: hangcheck detected gpu lockup rb 0! [ 625.829242] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: completed fence: 80902 [ 625.837377] msm 900000.mdss: [drm:hangcheck_handler] *ERROR* A530: submitted fence: 80903 [ 625.846301] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: hangcheck recover! [ 625.854630] msm 900000.mdss: [drm:recover_worker] *ERROR* A530: offending task: VTNext_ARM:sq0 (./VTNext_ARM64_Release.out -FULL) [ 625.862104] revision: 530 (5.3.0.2) [ 625.873679] rb 0: fence: 80902/80903 [ 625.876935] rptr: 3345 [ 625.880805] rb wptr: 3382 [ 625.883574] rb 1: fence: 0/0 [ 625.886253] rptr: 0
2.) I cannot successfully restart our application without getting a crash (log attached).
Thanks, Kim
-- With best wishes Dmitry _______________________________________________ Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU? 2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
Thanks, Kim
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
On 12/05/2023 20:39, Dmitry Baryshkov wrote:
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
In case the previous message doesn't get through because of the file size, I have uploaded it to the file server. Please find the patch at https://fileserver.linaro.org/s/irYEtnoaAct7pJg
Hi Dmitry,
Any progress with the cold bootup issue and/or speedup of GPU/CPU?
Paul, can we get an update on hours worked on this for this past month?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, May 12, 2023 10:43 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
On 12/05/2023 20:39, Dmitry Baryshkov wrote:
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
In case the previous message doesn't get through because of the file size, I have uploaded it to the file server. Please find the patch at https://fileserver.linaro.org/s/irYEtnoaAct7pJg
-- With best wishes Dmitry
Kim,
I’ll send that update when I’m back in the office next week.
Paul
On Thu, 25 May 2023 at 19:58, Kim Steiner < kim.steiner@sightlineapplications.com> wrote:
Hi Dmitry,
Any progress with the cold bootup issue and/or speedup of GPU/CPU?
Paul, can we get an update on hours worked on this for this past month?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, May 12, 2023 10:43 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt < paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
On 12/05/2023 20:39, Dmitry Baryshkov wrote:
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
In case the previous message doesn't get through because of the file size, I have uploaded it to the file server. Please find the patch at https://fileserver.linaro.org/s/irYEtnoaAct7pJg
-- With best wishes Dmitry
--
[image: Linaro] http://www.linaro.org/ Paul Neuhardt | *Sr. Program Manager* T: +44 0771 377 8664 paul.neuhardt@linaro.org glen.valante@linaro.org IRC: pneuhardt
Hi Kim
On 25/05/2023 19:58, Kim Steiner wrote:
Hi Dmitry,
Any progress with the cold bootup issue and/or speedup of GPU/CPU?
It took a way longer that we initially expected, but I kept on getting one of occasional issues during startup. With the attached set of patches I do no longer get the coldboot and/or VTNext restart issues. Please consider testing them. The patches are generated against 5.15krn tree.
Paul, can we get an update on hours worked on this for this past month?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, May 12, 2023 10:43 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
On 12/05/2023 20:39, Dmitry Baryshkov wrote:
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
In case the previous message doesn't get through because of the file size, I have uploaded it to the file server. Please find the patch at https://fileserver.linaro.org/s/irYEtnoaAct7pJg
-- With best wishes Dmitry
Hi Dmitry,
I applied all 12 patches you sent (in addition to the GPUPerformance patch), cold boot seems to be working. However, VTNext restart still has a hard crash.
Without the GPUPerformance patch, cold boot seems to work and VTNext restart also seems to work. I've only tested a few cold cycles and restarts of VTNext, but this is what I observe so far.
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Monday, May 29, 2023 1:37 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
Hi Kim
On 25/05/2023 19:58, Kim Steiner wrote:
Hi Dmitry,
Any progress with the cold bootup issue and/or speedup of GPU/CPU?
It took a way longer that we initially expected, but I kept on getting one of occasional issues during startup. With the attached set of patches I do no longer get the coldboot and/or VTNext restart issues. Please consider testing them. The patches are generated against 5.15krn tree.
Paul, can we get an update on hours worked on this for this past month?
Thanks, Kim
-----Original Message----- From: Dmitry Baryshkov dmitry.baryshkov@linaro.org Sent: Friday, May 12, 2023 10:43 AM To: Kim Steiner kim.steiner@sightlineapplications.com Cc: Jordan Holt jordan.holt@sightlineapplications.com; Paul Neuhardt paul.neuhardt@linaro.org; sightlineapplications@lists.linaro.org Subject: Re: [Sightlineapplications] Re: Low temperature GPU hang testing
On 12/05/2023 20:39, Dmitry Baryshkov wrote:
Hi Kim,
On 10/05/2023 16:18, Kim Steiner wrote:
Hi Dmitry,
Hope you are well!
1.) Any progress on the cold bootup issue and/or speedup of GPU/CPU?
I was OOO for several days during this week. Still WIP.
2.) I have not seen an email from you in regards to the (un)power patch you were planning on sending to us last week. Again, if it was easy to do, we could test quickly but this is low priority.
I have attached the no-heating,no-power-up patch. Took slightly more time than I expected to rip off the power regulation stuff.
In case the previous message doesn't get through because of the file size, I have uploaded it to the file server. Please find the patch at https://fileserver.linaro.org/s/irYEtnoaAct7pJg
-- With best wishes Dmitry
sightlineapplications@lists.linaro.org
-
Dmitry Baryshkov -
Glen Valante -
Jordan Holt -
Kim Steiner -
Paul Neuhardt -
Steve Olson