public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linux-kernel <linux-kernel@vger.kernel.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA C7 / VIA PC-1 (PC2500) anyone?
Date: Tue, 12 Jun 2007 12:39:10 +0300	[thread overview]
Message-ID: <466E69BE.405@vger.kernel.org> (raw)
In-Reply-To: <466E65A7.3000206@msgid.tls.msk.ru>

Michael Tokarev wrote:
> I bought a VIA PC2500 board a few days ago - this
> new series of their mobos,
> 
> This beast looks nice - after replacing their cooling
> system (that had a small fan on it) with larger but
> fanless, -- it becomes a almost real PC (1500MHz CPU),
> equipped with quite nice crypto and multimedia abilities,
> but with very low power consumption and very quiet.
> 
> But the thing is - it doesn't quite work.
> 
> It works generally - it boots, I can run my usual apps
> etc.  But on a random (yet frequent) basis it segfaults
> here and there.  For example:
> 
> $ man man
> Reformatting man(1), please wait...
> $ man man
> Segmentation fault
> $ man man
> Segmentation fault
> $ man man
> Segmentation fault
> $ man man
> Segmentation fault
> $ man man
> Reformatting man(1), please wait...
> $ _
> 
> (this is 100% idle machine, just booted).
> 
> (There are other - simple and comples - applications which
> inhibits this problem.  For example, it 99% reliable segfaults
> on compiling aic79xx_core.c file in kernel, while all the rest
> (in my configuration anyway) compiles, at least after second
> attempt).
> 
> It's definitely NOT memory issue - I tried several different
> memory modules (and different combinations) - the same results;
> I ran memtest86 for several days - no single error.
> 
> I've seen a thread here on LKML about C7 and C3 CPUs back in
> March this year - tried with patch from Andi titled
> "i386: Enable CX8/PGE CPUID bits early on VIA C3" - it didn't
> change anything (this board does not lock up - not when booting
> nor when doing something, -- just random applications are
> crashing randomly, and the crash is always SIGSEGV; there's
> _nothing_ in dmesg about that, too).
> 
> From all the above it seems like something's broke on the
> motherboard (I've no idea what it can be however - because
> memory testing - which also tests for CPU cache for exampe -
> shows no errors; testing disk controller/disk using md5 does
> not show errors either, except of occasional SIGSEGVs)..
> 
> However, being very curious about this, I tried installing
> 'doze on this machine - winXP.  And that one went just fine
> without any error so far -- i tried stress-testing it as far
> as I can imagine, running various applications and workloads, --
> no errors.
> 
> So I'm kinda.. stuck about what to do next.
> 
> Any.. idea, anyone? :)
> 
> Thanks!
> 
> /mjt

To me it looks like a wrong choice of gcc switches to user-mode programs. What
distribution are you using? try compiling failing programs from source with
conservative command line switches to gcc. See if things change.

Boaz


  reply	other threads:[~2007-06-12  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:21 VIA C7 / VIA PC-1 (PC2500) anyone? Michael Tokarev
2007-06-12  9:39 ` Linux-kernel [this message]
2007-06-12 12:19   ` Michael Tokarev
2007-06-12 10:43 ` Alan Cox
2007-06-12 12:04   ` Michael Tokarev
2007-06-12 10:44 ` Wander Winkelhorst
2007-06-12 11:58   ` Michael Tokarev
2007-06-12 12:54     ` Claas Langbehn
2007-06-12 13:01       ` Michael Tokarev
2007-06-12 21:59         ` Jan Engelhardt
2007-06-12 22:08           ` Dave Jones
2007-07-05 20:20 ` Michael Tokarev

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=466E69BE.405@vger.kernel.org \
    --to=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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