From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE, util-linux
Date: Mon, 08 Jul 2002 20:58:19 +0200 [thread overview]
Message-ID: <3D29E0CB.9040402@evision-ventures.com> (raw)
In-Reply-To: UTC200207081502.g68F2I701471.aeb@smtp.cwi.nl
Użytkownik Andries.Brouwer@cwi.nl napisał:
> Yesterday util-linux 2.11t was released.
> As always, comments are welcome.
>
> Wanted to continue some usb-storage work on 2.5 and
> recklessly booted 2.5.25. It survived for several hours,
> then deadlocked. Two filesystems turned out to be corrupted.
> Wouldn't mind if the rock solid 2.4 handling of HPT366
> was carefully copied to 2.5, that today quickly causes
> corruption and quickly deadlocks or crashes.
> [Yes, these are independent bugs. The fact that the current
> IDE code writes to random disk sectors is much more annoying
> than the fact that it crashes and deadlocks. This random
> writing is observed only on disks on the HPT366 card.]
Well the point is that the 2.5.25 is well behind whats
going on. It still contains IDE 93, which *is* broken.
Please hunt for IDE 94 + 95 + 96 [without 97]. This should
help. Anyway. My plan is to provide a 98 soon which will
be cummulative against 2.5.25, just to geive people a chance
to work on it again. But as it stands - *plain* 2.5.25 is
indeed very dangerous in this regard.
next prev parent reply other threads:[~2002-07-08 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 15:02 IDE, util-linux Andries.Brouwer
2002-07-08 16:05 ` Bartlomiej Zolnierkiewicz
2002-07-08 16:43 ` Roy Sigurd Karlsbakk
2002-07-08 17:38 ` Thunder from the hill
2002-07-08 18:58 ` Martin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-08 16:50 Andries.Brouwer
2002-07-08 17:10 ` Bartlomiej Zolnierkiewicz
2002-07-08 17:20 ` Andre Hedrick
2002-07-08 18:59 ` Martin Dalecki
2002-07-08 20:18 Andries.Brouwer
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=3D29E0CB.9040402@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
/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