From: Hui Zhou <hzhou@hzsolution.net>
To: linux-kernel@vger.kernel.org
Subject: Frustrating Random Reboots, seeking suggestions
Date: Fri, 9 Jun 2006 09:57:57 -0500 [thread overview]
Message-ID: <20060609145757.GB1640@smtp.comcast.net> (raw)
Hi Lists,
I understand this type of ask for help may be slightly off topic here,
but hoping for some clue to my desperation, here it goes:
I am running a linux machine with a self programmed pvr running on it.
All is well until I reinstalled the linux system a few weeks ago. Now
I am suffering from random reboots. The reboots does not leave any
debug messages or clues. After some isolation, I finally narrowed it
down to a blankscene marking program -- bkmark. Running bkmark against
any recording randomly reboots the computer. By random, I mean it may
complete sucessfully once, but repeating it for a few times, the
reboots will happen. On average, it reboots every 2 - 3 runs.
I am happy with and used to seg faults, which given time, I can
debug it. But this random reboots stuff is new to me and I have no
clues at all. How and why would a user land program reboots the
system?
I am running debian stable. Self compiled unpatched kernel 2.6.16.15
PREEMPT. Single Pentium 2.8GHz on Intel 865P motherboard. bkmark uses
libmpeg2 shared library. The source code is 471 lines, availible on
request. The same program runs without problem on the system before
(debian unstable) and even before (debian stable, but that was 5 months
ago) and even with the same kernel (2.6.14.6, I updated the kernel
after this problem occured).
More info is availible but I felt it may be inapprorate to post here
and honestly I have no clue which info is relavant. Any suggestions
or clues or advices on how to debug or narrow down the cause are very
appreciated.
Thank you.
--
Hui Zhou
next reply other threads:[~2006-06-09 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 14:57 Hui Zhou [this message]
2006-06-09 16:01 ` Frustrating Random Reboots, seeking suggestions Chase Venters
2006-06-10 2:37 ` Hui Zhou
2006-06-10 8:52 ` Ingo Oeser
2006-06-10 11:37 ` Hui Zhou
2006-06-10 15:27 ` Pavel Machek
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=20060609145757.GB1640@smtp.comcast.net \
--to=hzhou@hzsolution.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox