From: Vojtech Pavlik <vojtech@suse.cz>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 ate my filesystem on rw-mount, getting closer
Date: Sun, 14 Jan 2001 10:48:02 +0100 [thread overview]
Message-ID: <20010114104802.A804@suse.cz> (raw)
In-Reply-To: <20010114094447.A365@suse.cz> <Pine.LNX.4.30.0101140937470.6203-100000@svea.tellus>
In-Reply-To: <Pine.LNX.4.30.0101140937470.6203-100000@svea.tellus>; from tori@tellus.mine.nu on Sun, Jan 14, 2001 at 09:45:09AM +0100
On Sun, Jan 14, 2001 at 09:45:09AM +0100, Tobias Ringstrom wrote:
> On Sun, 14 Jan 2001, Vojtech Pavlik wrote:
> > On Sat, Jan 13, 2001 at 11:36:13PM +0100, Tobias Ringstrom wrote:
> >
> > > I have now tried the SAMSUNG VG34323A disk with two other controllers at
> > > home (Promise ATA100 an VIA vt82c686a rev 0x22, both on an ASUS A7V
> > > motherboard), and there are no problems to be found with DMA enabled.
> > > Streaming 10 MB/s without glitches.
> >
> > So the drive *did* work on the vt82c686a in the A7V board? You tested it
> > both on the Promise and on the 686a? But doesn't work on the 686a in
> > your other board?
>
> Yes, on both the Promise and on the 686a. But the device revisions are
> different. The machine that does NOT work:
>
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 1b)
> 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
>
> The machine that works:
>
> 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
> 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)
>
> The one the works is a 1 GHz Athlon, and the other is an 800 MHz
> Pentium-III.
>
> > > no matter what cable I use. When I get this, the machine does not recover
> > > most of the time, and I have to reset or power cycle.
> >
> > It should be able to recover in a couple (up to 10) minutes ...
>
> Who waits 10 minutes for a timeout? Can it be lowered?
It's not a 10 minute timeout, it's a shorter timeout retried many times.
Not my code, though - this is generic PCI IDE code, and is a huge mess.
> Expect another mail with the data you requested within a couple of hours.
Thanks a lot.
--
Vojtech Pavlik
SuSE Labs
-
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-14 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 9:15 2.4 ate my filesystem on rw-mount Tobias Ringstrom
2001-01-12 10:22 ` Alan Cox
2001-01-12 17:23 ` Martin Laberge
2001-01-12 19:51 ` Vojtech Pavlik
2001-01-12 19:49 ` Vojtech Pavlik
2001-01-13 8:12 ` Tobias Ringstrom
2001-01-13 14:35 ` Vojtech Pavlik
2001-01-13 16:20 ` Tobias Ringstrom
2001-01-13 22:36 ` 2.4 ate my filesystem on rw-mount, getting closer Tobias Ringstrom
2001-01-14 8:44 ` Vojtech Pavlik
2001-01-14 8:45 ` Tobias Ringstrom
2001-01-14 9:48 ` Vojtech Pavlik [this message]
2001-01-14 16:37 ` Tobias Ringstrom
2001-01-14 17:59 ` Tobias Ringstrom
2001-01-14 22:32 ` Vojtech Pavlik
2001-01-23 21:39 ` 2.4 ate my filesystem on rw-mount, summary Tobias Ringstrom
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=20010114104802.A804@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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