From: safemode <safemode@voicenet.com>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: 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:40:31 -0500 [thread overview]
Message-ID: <3A78945F.C82E7CAF@voicenet.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101312302410.14538-100000@svea.tellus>
Tobias Ringstrom wrote:
> On Wed, 31 Jan 2001, safemode wrote:
>
> > I'm wondering... Perhaps it's a problem motherboard specific. I'm
> > using the KA7 and saw pretty bad problems (extreme fs corruption)
> > and bad latency. Perhaps the K7V and the KT7's dont have this problem.
> > I dont see any of the problems with dma enabled on 2.2.x
>
> But are you using the same DMA mode in 2.2 as in 2.4? You can check that
> using hdparm -i, I believe.
>
> /Tobias
yea i know. . same mode i also had a big problem with DMA timeouts on
2.4 so .. i dont know what's up with 2.4 and my motherboard ... 2.2
hasn't shown a single irq or DMA error yet since going back to it.
currently 2.2.19-pre7 is using UDMA4 i just flashed the bios today so ..
hopefully that should have fixed any problems. I get 24MB/s each according
to hdparm -t on my hdd's and both are on the same channel. This is much
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.
my nbench performance under 2.2 is comparable to results for 1Ghz t-bird's so
i'm happy with 2.2. The only thing that would make me want to upgrade would
be latency patches. I'm convinced 2.4 has performance issues so i guess i'll
be using 2.2 until 2.5 begins. Is it really only 1 or 2 people having
this Via corruption problem? i doubt it's a bios problem because wouldn't
2.2 be effected by a bios bug if 2.4 is? In either case the changelogs dont
show any fixes for it.
-
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/
next prev parent reply other threads:[~2001-01-31 22:41 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 [this message]
2001-01-31 22:46 ` Alan Cox
2001-01-31 22:57 ` safemode
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=3A78945F.C82E7CAF@voicenet.com \
--to=safemode@voicenet.com \
--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