public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Miklos Szeredi <Miklos.Szeredi@eth.ericsson.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA C3 and random SIGTRAP or segfault
Date: Wed, 15 Jan 2003 13:23:01 +0000	[thread overview]
Message-ID: <20030115132301.GC1475@codemonkey.org.uk> (raw)
In-Reply-To: <200301151238.h0FCcwh11218@duna48.eth.ericsson.se>

On Wed, Jan 15, 2003 at 01:38:58PM +0100, Miklos Szeredi wrote:
 > 
 > Thanks, I'll check that out, though I'm a bit sceptical since the
 > crashes occur randomly not predictably, and that makes me feel it's
 > not because of an unimplemented instruction.
 > 
 > Also what about trace/breakpoint trap?  Can that be also generated by
 > an illegal instruction?

Hmm. My theory would explain SIGILL's, but if you're seeing others
as well, it could be something else. Check power supply is rated
high enough, cooling, (though cooling is usually less of an issue with C3s)
A run with memtest86 may also be worth trying.
		
		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-01-15 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15  9:29 VIA C3 and random SIGTRAP or segfault Miklos Szeredi
2003-01-15 12:23 ` Dave Jones
2003-01-15 12:38   ` Miklos Szeredi
2003-01-15 13:23     ` Dave Jones [this message]
2003-01-16  5:53   ` Glen Turner
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15 14:15 Larry Sendlosky
2003-01-15 14:47 ` Padraig
2003-01-15 15:56   ` Miklos Szeredi
2003-01-15 16:12     ` Jens Axboe
2003-01-15 16:13     ` Padraig
2003-01-15 16:26       ` Miklos Szeredi
2003-01-20  7:30 ` Alan

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=20030115132301.GC1475@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=Miklos.Szeredi@eth.ericsson.se \
    --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