public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hui Zhou <hzhou@hzsolution.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Frustrating Random Reboots, seeking suggestions
Date: Fri, 9 Jun 2006 21:37:19 -0500	[thread overview]
Message-ID: <20060610023719.GA10857@smtp.comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0606091058320.4969@turbotaz.ourhouse>

On Fri, Jun 09, 2006 at 11:01:22AM -0500, Chase Venters wrote:
>On Fri, 9 Jun 2006, Hui Zhou wrote:
>>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.
>Try to knock out any hardware problems first (run memtest86, check for 
>high heat / crappy power).
>
>If you're still having trouble, purchase a serial cable. Plug it into 
>another computer with a terminal program. Enable serial console support in 
>your kernel (and on your kernel command line). When the kernel boots, use 
>SysRq on the serial console to turn the console messaging level up to 
>maximum. If you're lucky, you'll catch some sort of diagnostics message on 
>the serial console before this happens.
>

Thanks. memtest86 passes 6 times without errors. Serial console didn't 
show up anything (it just reboots). 

Anyway, I finally suspect the debian libmpeg binary is at fault. I 
manually build it from src and statically linked to the `bkmark' 
program. It seems cured the random reboots problem. It runs 
successfully for 4 times. However, the fifth time it ended up in a `D' 
state. The only system call it uses is libc file IO and some signal 
passing. Any comment on the cause?

-- 
Hui Zhou

  reply	other threads:[~2006-06-10  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 14:57 Frustrating Random Reboots, seeking suggestions Hui Zhou
2006-06-09 16:01 ` Chase Venters
2006-06-10  2:37   ` Hui Zhou [this message]
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=20060610023719.GA10857@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