From: A E Lawrence <adrian.lawrence@computing-services.oxford.ac.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ian@wehrman.com, mhaque@haque.net, adilger@turbolinux.com,
linux-kernel@vger.kernel.org
Subject: Re: EXT2-fs error
Date: Sat, 24 Feb 2001 22:30:36 +0000 [thread overview]
Message-ID: <3A98360C.C7258FA6@computing-services.oxford.ac.uk> (raw)
In-Reply-To: <E14Wi2k-00009c-00@the-village.bc.nu>
Alan Cox wrote:
>
> > I have seen similar problems on stock 2.4.2 a machine which has not run
> > 2.4.1.
>
> What disk controllers ? We really need that sort of info in order to see the
> pattern in the odd reports of corruption we get
Sorry:-
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
10) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at d000
Capabilities: [c0] Power Management version 2
With dma enabled. If this is a known problem on this chipset, that may
be the explanation.
ael
--
A E Lawrence
next prev parent reply other threads:[~2001-02-24 22:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 19:12 EXT2-fs error Ian Wehrman
2001-02-23 11:46 ` John Heil
2001-02-23 19:26 ` Alan Cox
2001-02-23 11:50 ` John Heil
2001-02-24 11:02 ` A E Lawrence
2001-02-24 16:59 ` Alan Cox
2001-02-24 22:30 ` A E Lawrence [this message]
2001-02-24 23:08 ` A E Lawrence
2001-02-25 20:52 ` A E Lawrence
2001-02-25 13:53 ` John Heil
2001-02-25 17:58 ` Mike Brown
-- strict thread matches above, loose matches on Subject: below --
2006-08-06 4:03 Kiah Tang
2006-08-06 8:37 ` Wolfgang Denk
2006-08-07 2:47 ` WCT Tang
2001-03-30 3:06 khromy
2001-03-30 6:57 ` Rogier Wolff
2001-04-02 23:13 ` Alan Cox
2001-03-30 13:49 ` Dale E Martin
2001-02-22 7:02 Mohammad A. Haque
2001-02-22 8:10 ` Andreas Dilger
2001-02-22 14:58 ` Mohammad A. Haque
2000-12-06 21:50 Ext2-fs error mkloppstech
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=3A98360C.C7258FA6@computing-services.oxford.ac.uk \
--to=adrian.lawrence@computing-services.oxford.ac.uk \
--cc=adilger@turbolinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ian@wehrman.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaque@haque.net \
/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.