From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: goemon@anime.net (Dan Hollis),
maxwax@mindspring.com (Maxwell Spangler),
oyhaare@online.no (Øystein Haare),
linux-kernel@vger.kernel.org
Subject: Re: Via chipset
Date: 15 Aug 2001 14:50:55 -0700 [thread overview]
Message-ID: <87snetat6o.fsf@pelerin.serpentine.com> (raw)
In-Reply-To: <E15X7Kc-0003xP-00@the-village.bc.nu>
In-Reply-To: <E15X7Kc-0003xP-00@the-village.bc.nu>
a> Actually I've talked to a VIA person about it - the problem is I
a> don't have clean concrete repeatably way to generate the problem
a> and generate it rapidly.
Right. The closest I've come to a reproducible setup is "keep the PCI
bus very busy and hope for the best". This yields roughly 1 bad byte
read out of 150 million for stock 2.4.7, or 1 per 400 million for
2.4.8-ac3.
With error rates like this, it's not likely to be easy to find.
<b
next prev parent reply other threads:[~2001-08-15 21:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 23:10 Via chipset Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox
2001-08-07 23:47 ` Larry McVoy
2001-08-08 9:16 ` Janne Pänkälä
2001-08-08 16:09 ` Marco Colombo
2001-08-15 3:25 ` Maxwell Spangler
2001-08-15 11:48 ` Alan Cox
2001-08-15 12:28 ` Bobby D. Bryant
2001-08-15 19:59 ` Dan Hollis
2001-08-15 20:16 ` Alan Cox
2001-08-15 20:27 ` Dan Hollis
2001-08-15 20:32 ` Alan Cox
2001-08-15 21:50 ` Bryan O'Sullivan [this message]
2001-08-16 15:35 ` Bob Martin
2001-08-16 21:09 ` Dan Hollis
2001-08-17 3:04 ` Adrian V. Bono
2001-08-20 22:52 ` Bob Martin
2001-08-08 1:54 ` Ignacio Vazquez-Abrams
[not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 16:46 Ryan C. Bonham
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13 ` Marco Colombo
2001-09-12 20:55 ` Anders Peter Fugmann
2001-09-14 17:29 ` Jussi Laako
2001-10-05 10:20 amit yajurvedi
2001-10-15 11:09 grouch
[not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
[not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
[not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
2001-10-17 11:45 grouch
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=87snetat6o.fsf@pelerin.serpentine.com \
--to=bos@serpentine.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=goemon@anime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxwax@mindspring.com \
--cc=oyhaare@online.no \
/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