linux-kernel - Re: VIA C7 / VIA PC-1 (PC2500) anyone?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Jun 2007 16:04:53 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: VIA C7 / VIA PC-1 (PC2500) anyone?

Alan Cox wrote:
> On Tue, 12 Jun 2007 13:21:43 +0400
> Michael Tokarev <mjt@....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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/