From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: ralf@uni-koblenz.de
Cc: Michael Engel <engel@numerik.math.uni-siegen.de>,
linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: ext2fs corruptions and other things ...
Date: Sun, 19 Jul 1998 11:00:32 +0200 [thread overview]
Message-ID: <19980719110032.00526@alpha.franken.de> (raw)
In-Reply-To: <19980719023421.A489@uni-koblenz.de>; from ralf@uni-koblenz.de on Sun, Jul 19, 1998 at 02:34:21AM +0200
On Sun, Jul 19, 1998 at 02:34:21AM +0200, ralf@uni-koblenz.de wrote:
> On Sun, Jul 19, 1998 at 12:53:14AM +0200, Michael Engel wrote:
> Quite some time Thomas commited a patch to arch/mips/kernel/irc.c which was
> actually supposed to fix the probing problem, maybe he can comment.
I couldn't even remember, that I did something in that area:-) I've looked
up in CVS, what I did there, and as far as I remeber it fixed autoprobing
for me (my NE2000 gets the interrupt via autoprobing). Maybe it's time
to check whether it still works.
> We actually had more reports about problems with filesystems on /dev/sdx
> on Indys. There seems to be a clear pattern of a bug, but for now I
> classify that one as lower priority.
I've never got any filesystem corruption on my Olli. And I've crashed it
pretty often, when doing the XF68_FBDev stuff.
Thomas.
--
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
[Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]
prev parent reply other threads:[~1998-07-19 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199807182253.AAA10366@jordan.numerik>
1998-07-19 0:34 ` ext2fs corruptions and other things ralf
1998-07-19 9:00 ` Thomas Bogendoerfer [this message]
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=19980719110032.00526@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=engel@numerik.math.uni-siegen.de \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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