From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: gphat@cafes.net (Cory Watson)
Cc: monniaux_nospam@arbouse.ens.fr (David Monniaux),
linux-kernel@vger.kernel.org
Subject: Re: more on VIA 686B (trials)
Date: Thu, 14 Jun 2001 19:10:22 +0100 (BST) [thread overview]
Message-ID: <E15AbZW-00054e-00@the-village.bc.nu> (raw)
In-Reply-To: <01061413111300.06452@achmed> from "Cory Watson" at Jun 14, 2001 01:11:13 PM
> Abit KT7A, kernel oops right after boot... :( Can be solved to turning off
> 'Enhance Chip Performance' in the BIOS, but then our chip performance is
> un'Enhance'd, and we can't have that! So back to the K6 kernel.
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 ?
Alan
next prev parent reply other threads:[~2001-06-14 18:12 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 [this message]
2001-06-14 18:29 ` Cory Watson
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=E15AbZW-00054e-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gphat@cafes.net \
--cc=linux-kernel@vger.kernel.org \
--cc=monniaux_nospam@arbouse.ens.fr \
/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).