From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
To: John Jasen <jjasen@datafoundation.com>
Cc: Andre Hedrick <andre@linux-ide.org>,
linux-kernel@vger.kernel.org, axp-list@redhat.com,
denis@datafoundation.com
Subject: Re: 2.4.x/alpha/ALI chipset/IDE problems summary Re: 2.4.1 not fully sane on Alpha - file systems
Date: Thu, 15 Feb 2001 12:48:37 -0700 [thread overview]
Message-ID: <20010215124837.B13755@ellpspace.math.ualberta.ca> (raw)
In-Reply-To: <Pine.LNX.4.10.10102011415070.17898-100000@master.linux-ide.org> <Pine.LNX.4.30.0102151247410.4654-100000@flash.datafoundation.com>
In-Reply-To: <Pine.LNX.4.30.0102151247410.4654-100000@flash.datafoundation.com>; from John Jasen on Thu, Feb 15, 2001 at 12:49:29PM -0500
On Thu, Feb 15, 2001 at 12:49:29PM -0500, John Jasen wrote:
>
> Well, the situation is improving, I suppose ...
>
> Under kernel 2.4.0 and 2.4.1, a dd of about 10000 4k blocks would cause
> the system to go technicolor and lock up.
On UP1100 which I have here somehow this looks a bit different _after_
I put on it the latest SRM and used this "magic incantation" from
Hyung Min SEO ('d -l 801fe0000ac d' at SRM prompt to modify firmware).
I copied from disk to disk directory tries with some 150 MB of data
in these and no ill effects.
OTOH things are still wobbly. This shows up in this that trying to
run e2fsck on a dirty file system while booting one 2.4.1 is likely
to come up with all kind of errors in a file sytstem requiring manual
interactions. If one breaks this process and repeats an exercise
on the same file system, but booting this time 2.2.18, then things
check out without any incidents. Once clean file systems can be
used with 2.4.1 again and no problems are reported.
I really do not see any kernel problems with 2.2 series kernels and IDE
patches.
> Now, under 2.4.1-ac13, at about 11000 blocks, it goes technicolor, but
> doesn't lock up until somewhere between 13000 and 20000.
I got various lockups but no "technicolor" on any occasion. Recently
I even got a picture with X and G450 Matrox card although one can
be very careful not to look at it a wrong angle or a power button will
be the only way out.
Michal
next prev parent reply other threads:[~2001-02-15 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 6:49 2.4.1 not fully sane on Alpha - file systems Michal Jaegermann
2001-02-01 15:46 ` John Jasen
2001-02-01 16:23 ` Michal Jaegermann
2001-02-01 20:38 ` 2.4.x/alpha/ALI chipset/IDE problems summary " John Jasen
2001-02-01 22:18 ` Andre Hedrick
2001-02-02 16:30 ` John Jasen
2001-02-15 17:49 ` John Jasen
2001-02-15 19:48 ` Michal Jaegermann [this message]
2001-02-15 20:15 ` John Jasen
2001-02-15 20:47 ` Michal Jaegermann
2001-02-15 20:59 ` John Jasen
2001-02-02 7:39 ` Michal Jaegermann
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=20010215124837.B13755@ellpspace.math.ualberta.ca \
--to=michal@ellpspace.math.ualberta.ca \
--cc=andre@linux-ide.org \
--cc=axp-list@redhat.com \
--cc=denis@datafoundation.com \
--cc=jjasen@datafoundation.com \
--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