public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA C7 / VIA PC-1 (PC2500) anyone?
Date: Tue, 12 Jun 2007 16:04:53 +0400	[thread overview]
Message-ID: <466E8BE5.3030903@msgid.tls.msk.ru> (raw)
In-Reply-To: <20070612114345.07ab60f6@the-village.bc.nu>

Alan Cox wrote:
> On Tue, 12 Jun 2007 13:21:43 +0400
> Michael Tokarev <mjt@tls.msk.ru> 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.
> 
> That is usually memory or motherboard timings. memtest86+ will miss a lot
> of problems on these boards for some reason I don't really fathom
> although its still a worthwhile test you did

Hmm.  Memory or motherboard timings.  There are several options in BIOS
about this.  I'll try to experiment.  The only prob - it seems - is that
BIOS only allows INcreasing speeds (frequencies etc), not DEcreasing them.
More, the BIOS does not have CPU frequency control at all - only PCI bus
frequency and memory frequency.  Memory DIMMs are 667 MHz (PC5300), while
the mobo accepts 533MHz (PC4200?), and are running at 533MHz (according to
BIOS).

But in any way, I'll try to experiment here.

> I'd be interested to knowwhat the following do
> 
> Bad RAM check:
> 	Boot with mem= to limit to the bottom 256MB of RAM
> 	(Windows tends to use different areas of RAM to Linux the most so
> 	your report fits that)
> 
> Stress testing:
> 	Go into X in a high resoution, starting running a continuous
> 	copy to or from disk and see if its suddenely much less stable

Okay, running with mem=128m now, copying linux kernel source and
removing it, 10 processes in parallel.

So far, I see the same random SIGSEGVs - not from cp and rm, but from
"usual" suspect - man(1) command segfaults pretty frequently as before ;)

> Disabling power management

Wonder how to disable it... :)  I already turned off all power management
stuff in BIOS I was able to find.

Thanks!

/mjt

  reply	other threads:[~2007-06-12 12:05 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
2007-06-12 12:19   ` Michael Tokarev
2007-06-12 10:43 ` Alan Cox
2007-06-12 12:04   ` Michael Tokarev [this message]
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=466E8BE5.3030903@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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