From: Bill Gatliff <bgat@billgatliff.com>
To: Gary Thomas <gary@mlbassoc.com>, linux-omap@vger.kernel.org
Subject: Re: Restart after 4 min of operation?
Date: Tue, 03 Nov 2009 11:47:38 -0600 [thread overview]
Message-ID: <4AF06CBA.3040609@billgatliff.com> (raw)
In-Reply-To: <4AF01901.2050100@mlbassoc.com>
Gary Thomas wrote:
> On 11/02/2009 08:35 PM, Bill Gatliff wrote:
>> Guys:
>>
>>
>> Can someone give me any ideas as to why my Beagleboard-like platform
>> would spontaneously restart after precisely four minutes of operation?
>> No OOPS, no nothing. This is with 2.6.32-rc5.
>>
>
> BeagleBoard like? More details are probably required for much help.
>
> How do you power it? My BeagleBoard is powered via the OTG. I've
> seen it reset if I hang too much on the USB host port (exceed the
> meager power budget)
It's a clone of a BeagleBoard, but with more and friendlier I/O. CUS
package, and they use the TPS65023RSB power supply manager. I'm not
ready to bury anyone in more details yet, since it's a client's hardware
and I feel like I'm imposing already... :)
When I boot it to my kernel, which is based on 2.6.32-rc5, it comes up
fine and then for no apparent reason after four minutes goes through a
reset again. I know it's approximately the same each time, because I
have uptime running in a loop so that I can conveniently see when it
dies. The very same tree boots and runs properly on a true BeagleBoard
rev C.
What's even more wierd is that even when sitting at the u-boot prompt
before launching any kernel at all, the board does the same thing---
spontaneous reset after about four minutes. The client provided me the
u-boot image, and it says it's a modified one from the OMAP3EVM--- it
even provides that machine id.
The above behavior makes me suspect hardware, but read on before you agree.
Finally, the client provided me a kernel of unknown origin (it says it's
a 2.6.29-rc2) that appears to run fine---- no hiccup at 4 minutes. Of
course, that kernel doesn't have the features they need. I'm going over
it now to see if there's a magic bit somewhere that mine is missing, but
I'm at a bit of a loss to explain what I'm seeing right now.
Anyone have any ideas? Bizzare.
(BTW, nice to hear from you again, Gary! It's been a while.)
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2009-11-03 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 3:35 Restart after 4 min of operation? Bill Gatliff
2009-11-03 11:50 ` Gary Thomas
2009-11-03 17:47 ` Bill Gatliff [this message]
2009-11-03 17:53 ` Gadiyar, Anand
2009-11-03 18:37 ` Bill Gatliff
2009-11-03 18:40 ` Gadiyar, Anand
2009-11-03 18:41 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF06CBA.3040609@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=gary@mlbassoc.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.