From: John Jasen <jjasen@datafoundation.com>
To: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
Cc: Andre Hedrick <andre@linux-ide.org>,
<linux-kernel@vger.kernel.org>, <axp-list@redhat.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 15:15:01 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.30.0102151513170.4654-100000@flash.datafoundation.com> (raw)
In-Reply-To: <20010215124837.B13755@ellpspace.math.ualberta.ca>
On Thu, 15 Feb 2001, Michal Jaegermann 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.
I retried the mysticism and incantations (d -l 801fe0000ac d) at the srm
prompt, and the machine locked on fsck, under kernel 2.4.1-ac13.
I don't care about X on this system, all that much, honestly.
-- John
next prev parent reply other threads:[~2001-02-15 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 6:49 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
2001-02-15 20:15 ` John Jasen [this message]
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=Pine.LNX.4.30.0102151513170.4654-100000@flash.datafoundation.com \
--to=jjasen@datafoundation.com \
--cc=andre@linux-ide.org \
--cc=axp-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@ellpspace.math.ualberta.ca \
/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
all inboxes | Powered by JetHome®