All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spontaneous reboots with latest 2.6.16 RC-s
Date: Sun, 5 Mar 2006 17:29:05 +0100	[thread overview]
Message-ID: <20060305162905.GC20287@stusta.de> (raw)
In-Reply-To: <Pine.SOC.4.61.0603021501560.23598@math.ut.ee>

On Thu, Mar 02, 2006 at 03:19:09PM +0200, Meelis Roos wrote:
> I have had 3 spontaneous reboots in last week with 2.6.16-rc[45] 
> timescale kernels. Could be kernel or X or hardware, not sure yet. When 
> they happened, mplayer was used to play some movie fullscreen with 
> Matrox G400 and XVideo (X.org 6.9) and there was slight disk and network 
> activity. This reboot is not reproducible at will, it will only happen 
> sometimes.
> 
> This is a lone home computer so no serial console.
> 
> Plain Duron PC with up-to-date Debian unstable. Have kept it mostly up 
> to date with the exception that I kept using X.org 6.8.2 for a long time 
> before switching to X.org 6.9 - so it might be X problem instead and it 
> might only have surfaced after I restarted after upgrading to X.org 6.9.
> 
> Earlier 2.6.16 RC-s (or git snapshots from that time) were OK, where OK 
> means that I did not see any problems.
> 
> 2.6.16-rc2 was stable for 11 days
> 2.6.16-rc3-g5552... was OK for 2 days
> 2.6.16-rc3-gab47... rebooted
> 2.6.16-rc4-g9e95... rebooted
> 2.6.16-rc5-gb1e2... rebooted (todays snapshot)
> 
> /proc/interrupts, lspci -vvvn and dmesg of a bootup are below. Any ideas 
> if this could be something with a kernel?
>...

It could be, but it could also be hardware.
Does the machine survive a night of memtest86?

Please turn on all debugging options in the kernel.

It's extremely unlikely that it's in any way related, but is this the 
machine you reported the psmouse problems for?

Can you find a pattern that triggers the problem with a nearly 100% 
probability? E.g. "24 hours of mplayer fullscreen"?
If yes, check 2.6.16-rc3-g5552 if it really is OK, and then do a binary 
search for the commit that causes your problem.

> Meelis Roos (mroos@linux.ee)

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-03-05 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 13:19 spontaneous reboots with latest 2.6.16 RC-s Meelis Roos
2006-03-05 16:29 ` Adrian Bunk [this message]
2006-03-06 11:34   ` Meelis Roos
2006-03-08 12:07   ` Meelis Roos
2006-03-20  7:29   ` Meelis Roos
2006-03-20  7:53     ` Josef Sipek

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=20060305162905.GC20287@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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.