public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John R Lenton <john@grulic.org.ar>
To: linux-kernel@vger.kernel.org
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Sat, 5 May 2001 03:43:57 -0300	[thread overview]
Message-ID: <20010505034357.A604@grulic.org.ar> (raw)
In-Reply-To: <E14vmpN-000822-00@the-village.bc.nu> <006e01c0d4e9$3c0bd210$0300a8c0@methusela> <3AF2F07E.545BBDDB@mail.utexas.edu>
In-Reply-To: <3AF2F07E.545BBDDB@mail.utexas.edu>; from bdbryant@mail.utexas.edu on Sat, May 05, 2001 at 12:10:06AM +0600

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Sat, May 05, 2001 at 12:10:06AM +0600, Bobby D. Bryant wrote:
> They do boot PIII kernels reliably for all those variants, though they still
> suffer occasional oopses, hangs, or crashes (as discussed in other threads).

and as happens with my SMP pIII VIA-based boxed (and I've finally
fixed the memory, so I no longer get the oopses, just solid
hardware hangs).

> However (and here's the part I haven't mentioned before), yesterday I switched
> one of them to a new mb with a non-VIA chipset (Asus A7A266), and it booted the
> first Athlon kernel I tried (2.4.4).  No other changes to .config, same
> processor as before, same memory, same disks, same video, same case, same power
> cord, you name it.

damn. I guess the saving of 200$ on the MSI has probably been
300$ down the drain :(

-- 
John Lenton (john@grulic.org.ar) -- Random fortune:
If you treat people right they will treat you right -- 90% of the time.
		-- Franklin Delano Roosevelt

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-05-05  6:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04 17:22 REVISED: Experimentation with Athlon and fast_page_copy Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26   ` Aaron Tiensivu
2001-05-04 18:10     ` Bobby D. Bryant
2001-05-05  6:43       ` John R Lenton [this message]
2001-05-05  7:20         ` Alan Cox
2001-05-07  1:26           ` John R Lenton
2001-05-07  1:30             ` Jeremy
2001-05-05  0:26     ` Joseph Carter
2001-05-05  3:51       ` Chris Wedgwood
2001-05-05  4:08         ` Seth Goldberg
     [not found]           ` <20010505163204.A29622@metastasis.f00f.org>
2001-05-05  5:03             ` Athlon and fast_page_copy: What's it worth ? :) Seth Goldberg
2001-05-05  6:20               ` Mark Hahn
2001-05-05  9:15                 ` Tom Leete
2001-05-05  7:17               ` Alan Cox
2001-05-05 14:19               ` Jonathan Morton
2001-05-05 14:41                 ` Alan Cox
2001-05-05 15:17                 ` Jonathan Morton
2001-05-08 21:16               ` Arjan van de Ven
2001-05-05  5:45         ` REVISED: Experimentation with Athlon and fast_page_copy Joseph Carter
2001-05-09  2:11   ` Tom Leete
2001-05-09  8:49     ` Alan Cox
2001-05-09 11:38       ` Tom Leete
2001-05-09 12:38         ` Alan Cox
2001-05-09 13:02           ` Tom Leete
  -- strict thread matches above, loose matches on Subject: below --
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15   ` Arjan van de Ven
2001-05-05  2:28 Dieter Nützel
2001-05-05  7:13 ` Alan Cox
2001-05-09 23:56   ` Dieter Nützel
2001-05-05 17:34 Jeremy

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=20010505034357.A604@grulic.org.ar \
    --to=john@grulic.org.ar \
    --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