Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello All,
I am running linux in an embedded environment. Once every couple of days my target reboots. Is there a way to know what the cause was ? I have 6 target boards running same code, and only 1 had this problem over last 2 days. Its not board related, as I have seen it do on other boards. Same boards when loaded with previous rev of code, didnt do this. I am looking for something that gets logged before the system reboots.
We can try to help, but read the "Question Guidelines" link in my posting signature. You are not providing us with ANY useful details (version/distro of Linux, type of board, any updates lately, etc.), that would help us to help you. We can't guess.
Your system logs *MAY* have something in them, but we can't tell you whether or not to use journalctl to view them, or for you to look in /var/log/messages or the like, since we don't know what Linux you're using. Even then, if it's hardware related, there may be nothing to see.
Guess you could look closely at the boards to decide if they are in fact the same in all ways. That one may have a different chip or revision level or other soft/firmware.
How did you test that the image is exactly what you want on these boards?
Telling us what changes are in the code may help, what part of the system is affected?
Errors can go to various locations provided the board has it set to record, provided it has the ability to record. Otherwise there will be no record.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.