From: Cory Watson <gphat@cafes.net>
To: linux-kernel@vger.kernel.org
Subject: Re: more on VIA 686B (trials)
Date: Thu, 14 Jun 2001 13:29:44 -0500 [thread overview]
Message-ID: <01061413294401.06452@achmed> (raw)
In-Reply-To: <E15AbZW-00054e-00@the-village.bc.nu>
In-Reply-To: <E15AbZW-00054e-00@the-village.bc.nu>
On Thursday 14 June 2001 01:10 pm, Alan Cox wrote:
> And praying it doesnt go wrong on you - has it not occurred to you that the
> extremely high throughput copies that the mmx copy we use causes will
> occasionally happen by chance and get you anyway ?
Yeah, it's occurred to me, but it's yet to happen. I fought with the thing
for 48 hours, and after settling on a K6 kernel w/'Enhanced' enabled, I've
not had a single problem. I suppose it's possible that I've not seen the
problem, but I've put this box through it's paces many times over since I
settled. I gave it another go with 2.4.6-pre3 this morning, hoping something
had snuck in ;)
--
Cory 'G' Watson
You know what we need, Hobbes? We need an attitude. Yeah, you can't be cool
if you don't have an attitude. -- Calvin
next prev parent reply other threads:[~2001-06-14 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 17:44 more on VIA 686B (trials) David Monniaux
2001-06-14 18:11 ` Cory Watson
2001-06-14 18:10 ` Alan Cox
2001-06-14 18:29 ` Cory Watson [this message]
2001-06-14 18:11 ` Rachel Greenham
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=01061413294401.06452@achmed \
--to=gphat@cafes.net \
--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