From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Pawel Kot <pkot@linuxnews.pl>,
lkml <linux-kernel@vger.kernel.org>,
Andre Hedrick <andre@serialata.org>
Subject: Re: Another -pre
Date: Mon, 3 Jun 2002 20:27:08 -0300 [thread overview]
Message-ID: <20020603232707.GI6062@conectiva.com.br> (raw)
In-Reply-To: <Pine.LNX.4.44.0206031155200.4146-100000@freak.distro.conectiva> <1023149710.6773.82.camel@irongate.swansea.linux.org.uk>
Em Tue, Jun 04, 2002 at 01:15:10AM +0100, Alan Cox escreveu:
> With the current code I've got these items on my list I class as
> problematic.
you mean with 2.4.19-pre9 or with 2.4.19-pre9-ac3?
> 1 Weird corruption report with AMD chipset in PIO mode
Oh, I'm not alone ;) Well, up to now it _seems_ that ext3 is saving my day,
but it only happened two time after I upgraded to 2.4.19-pre8-ac5, none after
I upgraded to 2.4.19-pre9-ac3, but I can't manage to make 'hdparm -X68 /dev/hdd'
to work :( I have already sent detailed information to Andre and discussed
and tried several things sugested in a irc chat.
Short description: I use ext3 over raid0, using /dev/hda4 and /dev/hdd1,
/dev/hdc has a CDRW drive, mostly unused, /dev/hdb has nothing, two times
/dev/hda stopped responding, not reproducible AFAIT.
- Arnaldo
next prev parent reply other threads:[~2002-06-03 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 14:23 Another -pre Marcelo Tosatti
2002-06-03 15:47 ` Pawel Kot
2002-06-03 14:55 ` Marcelo Tosatti
2002-06-03 16:02 ` Pawel Kot
2002-06-03 16:13 ` Marcelo Tosatti
2002-06-04 0:15 ` Alan Cox
2002-06-03 23:24 ` Matt Simonsen
2002-06-08 19:42 ` Andre Hedrick
2002-06-03 23:27 ` Arnaldo Carvalho de Melo [this message]
2002-06-04 0:10 ` Andreas Dilger
2002-06-04 8:35 ` Daniela Engert
2002-06-08 19:30 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 2:46 Neil Brown
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=20020603232707.GI6062@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@serialata.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pkot@linuxnews.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.