From: Rene Rebe <rene.rebe@gmx.net>
To: alan@lxorguk.ukuu.org.uk
Cc: calin@ajvar.org, hassani@its.caltech.edu, linux-kernel@vger.kernel.org
Subject: Re: Athlon Optimization Problem
Date: Mon, 28 Jan 2002 21:28:30 +0100 (CET) [thread overview]
Message-ID: <20020128.212830.846943574.rene.rebe@gmx.net> (raw)
In-Reply-To: <E16VIKU-0001f7-00@the-village.bc.nu>
In-Reply-To: <Pine.LNX.4.30.0201281452480.9637-200000@rtlab.med.cornell.edu> <E16VIKU-0001f7-00@the-village.bc.nu>
On: Mon, 28 Jan 2002 20:24:38 +0000 (GMT),
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Im still not convinced touching the register on the 266 chipset at 0x95 is
> correct. I now have several reports of boxes that only work if you leave it
> alone
We have a Druon-700 box based on the "Asus A7V" lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0a.0 Multimedia audio controller: Avance Logic Inc. ALS4000 Audio Chipset
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 02)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
With an Athlon optimized 2.4.[16,17,18-pre7] all programs are getting
sig-11s everytime. Even mem=nopentium doesn't help, using generic i386
code generation seems to help. An Athlon optimized 2.4.4 kernel seems
also to run fine (and running memtest86 for some hours did not showed
a memory error ...).
> Alan
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://drocklinux.dyndns.org/rene/
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2002-01-28 20:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 9:07 Steven Hassani
2002-01-28 10:07 ` Steven Hassani
2002-01-28 19:56 ` Calin A. Culianu
2002-01-28 20:24 ` Alan Cox
2002-01-28 20:53 ` Calin A. Culianu
2002-01-28 21:08 ` Alan Cox
2002-01-29 21:05 ` Calin A. Culianu
2002-01-29 21:19 ` Trever L. Adams
2002-01-29 23:26 ` Alan Cox
2002-01-30 16:04 ` Calin A. Culianu
2002-01-30 22:12 ` Bill Davidsen
2002-01-30 23:10 ` Alan Cox
2002-01-29 8:07 ` Daniel Nofftz
2002-01-29 20:56 ` Calin A. Culianu
2002-01-29 21:22 ` Calin A. Culianu
2002-01-29 23:04 ` Daniel Nofftz
2002-01-29 23:27 ` Calin A. Culianu
2002-01-30 9:05 ` Daniel Nofftz
2002-01-29 22:59 ` Daniel Nofftz
2002-01-29 17:04 ` Paul G. Allen
2002-01-29 17:17 ` Rene Rebe
2002-01-28 20:28 ` Rene Rebe [this message]
2002-01-29 0:46 ` Denis Vlasenko
[not found] <Pine.LNX.4.33.0201301838520.23104-100000@coffee.psychology.mcmaster.ca>
2002-02-04 20:28 ` Bill Davidsen
2002-02-05 3:22 Serguei Miridonov
2002-02-05 12:56 ` Denis Vlasenko
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=20020128.212830.846943574.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=calin@ajvar.org \
--cc=hassani@its.caltech.edu \
--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
all inboxes | Powered by JetHome®