public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: safemode <safemode@voicenet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tobias Ringstrom <tori@tellus.mine.nu>,
	Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
	David Raufeisen <david@fortyoz.org>,
	Vojtech Pavlik <vojtech@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: VT82C686A corruption with 2.4.x
Date: Wed, 31 Jan 2001 17:57:45 -0500	[thread overview]
Message-ID: <3A789869.B05506FB@voicenet.com> (raw)
In-Reply-To: <E14O60w-0003IO-00@the-village.bc.nu>

Alan Cox wrote:

> > better than i ever got with 2.4 even when only one drive was on a channel.
> > Right now my k7-2 750 is at 849mhz with a FSB of 114Mhz and PCI at 34Mhz.
>
> Hint: people who overclock machines get suprising odd results and bad stuff
> happens. Please dont waste developers time unless you can reproduce it at
> the intended speed for the components

Like i said .. i just did that within the last 5 min   it has nothing to do
with any problems i've been talking about

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-31 22:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10101301743180.30535-100000@coffee.psychology.mcmaster.ca>
2001-01-31  1:18 ` VT82C686A corruption with 2.4.x David D.W. Downey
2001-01-31  2:04   ` David D.W. Downey
2001-01-31  7:36     ` Vojtech Pavlik
2001-01-31  7:55       ` David Raufeisen
2001-01-31  9:48         ` safemode
2001-01-31 11:43           ` Vojtech Pavlik
2001-01-31 12:54           ` Mark Hahn
2001-01-31 19:58             ` David Riley
2001-02-01 12:51               ` David D.W. Downey
2001-01-31 20:01             ` safemode
2001-01-31 22:04               ` Tobias Ringstrom
2001-01-31 22:40                 ` safemode
2001-01-31 22:46                   ` Alan Cox
2001-01-31 22:57                     ` safemode [this message]
2001-02-01  6:31                       ` Vojtech Pavlik
2001-02-01  0:46                   ` Byron Stanoszek
2001-02-01  1:52                     ` safemode
2001-02-01  6:52                       ` Vojtech Pavlik
2001-02-01 11:32                         ` safemode
2001-02-01 16:46                           ` Byron Stanoszek
2001-02-01 18:06                             ` Vojtech Pavlik
2001-02-01 18:20                               ` Byron Stanoszek
2001-02-01 20:51                                 ` Vojtech Pavlik
2001-02-01 21:51                                   ` safemode
2001-02-01 21:56                               ` Alan Chandler
2001-02-01  6:39                     ` Vojtech Pavlik
2001-01-31 11:39         ` Vojtech Pavlik
2001-01-31 15:41           ` David D.W. Downey
2001-01-30 13:40 Nicholas Knight
2001-01-30 15:03 ` Tobias Ringstrom
2001-01-30 19:51   ` David D.W. Downey
2001-01-30 20:53     ` David Raufeisen

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=3A789869.B05506FB@voicenet.com \
    --to=safemode@voicenet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=david@fortyoz.org \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tori@tellus.mine.nu \
    --cc=vojtech@suse.cz \
    /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