From: Rob Landley <landley@webofficenow.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA Southbridge bug (Was: Crash on boot (2.4.5))
Date: Mon, 9 Jul 2001 12:48:59 -0400 [thread overview]
Message-ID: <01070912485904.00705@localhost.localdomain> (raw)
In-Reply-To: <E15JIVD-0000Qc-00@the-village.bc.nu>
In-Reply-To: <E15JIVD-0000Qc-00@the-village.bc.nu>
On Sunday 08 July 2001 13:37, Alan Cox wrote:
> > > possible on the memory bus. Several people have reported that machines
> > > that are otherwise stable on the bios fast options require the proper
> > > conservative settings to be stable with the Athlon optimisations
> >
> > Do we need patch to memtest to use 3dnow?
>
> Possibly yes. Although memtest86 really tries to test for onchip not bus
> related problems
What else tends to fail on the motherboard that might be easy to test for?
Processor overheating? (When the thermometer circuitry's there, anyway.)
Something to do with DMA? (Would DMA to/from a common card like VGA catch
chipset-side DMA problems?) There was an SMP exception thing floating by
recently, is that common and testable?
I know there's a lot of funky peripheral combinations that behave strangely,
but without opening that can of worms what kind of common problems on the
motherboard itself might be easy to test for in a "run this overnight and see
if it finds a problem with your hardware" sort of way?
Rob
(P.S. What kind of CPU load is most likely to send a processor into overheat?
(Other than "a tight loop", thanks. I mean what kind of instructions?)
This is going to be CPU specific, isn't it? Our would a general instruction
mix that doesn't call halt be enough? It would need to keep the FPU busy
too, wouldn't it? And maybe handle interrupts. Hmmm...)
I wonder... The torture test Tom's Hardware guide uses for processor
overheating is GCC compiling the Linux kernel. (That's what caught the
Pentium III 1.13 gigahertz instability when nothing else would.) I wonder,
maybe if a stripped down subset of a known version of GCC and a known version
of the kernel were running from a ramdisk... It USED to fit in 8 megs with
no swap, might still fit in 32 with a decent chunk of kernel source. Throw
the compile in a loop, add in a processor temperature detector daemon to kill
the test and HLT the system if the temperature went too high...
I wonder what bits of the kernel GCC actually needs to run these days?
(System V inter-process communication? sysctl support? Hmmm... Would
2.4.anything be a stable enough base for this yet, or should it be 2.2.19?
Is 2.4 still psychotic with less swap space than ram (I.E. no swap space at
all)?)
Off to play...
Still Rob.
next prev parent reply other threads:[~2001-07-10 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 6:17 Crash on boot (2.4.5) Andy Ward
2001-06-25 6:32 ` VIA Southbridge bug (Was: Crash on boot (2.4.5)) Steven Walter
2001-06-25 7:06 ` Alan Cox
2001-06-30 13:58 ` Pavel Machek
2001-07-08 17:37 ` Alan Cox
2001-07-09 16:48 ` Rob Landley [this message]
2001-07-10 9:17 ` Ville Herva
2001-07-10 15:28 ` Hardware testing [was Re: VIA Southbridge bug (Was: Crash on boot (2.4.5))] Rob Landley
2001-07-11 4:18 ` Albert D. Cahalan
2001-07-11 8:43 ` Ville Herva
2001-07-11 9:11 ` Vojtech Pavlik
2001-07-11 15:05 ` Rob Landley
2001-07-12 6:57 ` Ville Herva
2001-07-10 21:24 ` VIA Southbridge bug (Was: Crash on boot (2.4.5)) Adam Sampson
2001-07-11 8:32 ` Ville Herva
2001-07-11 9:03 ` Eyal Lebedinsky
2001-06-25 19:55 Andy Ward
2001-06-25 19:57 Andy Ward
2001-06-25 20:27 ` David Grant
2001-06-26 9:10 ` pazke
2001-07-10 9:12 David Balazic
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=01070912485904.00705@localhost.localdomain \
--to=landley@webofficenow.com \
--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;
as well as URLs for NNTP newsgroup(s).