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
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 13:47:47 -0700 [thread overview]
Message-ID: <20010215134747.A13942@ellpspace.math.ualberta.ca> (raw)
In-Reply-To: <20010215124837.B13755@ellpspace.math.ualberta.ca> <Pine.LNX.4.30.0102151513170.4654-100000@flash.datafoundation.com>
In-Reply-To: <Pine.LNX.4.30.0102151513170.4654-100000@flash.datafoundation.com>; from John Jasen on Thu, Feb 15, 2001 at 03:15:01PM -0500
On Thu, Feb 15, 2001 at 03:15:01PM -0500, John Jasen wrote:
>
> 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.
Like I wrote - I did not get to locks on fsck but then stuff was weird
and if I would press sufficiently long maybe I would. I still had some
use for my file systems so I did not try hard enough. Maybe we need
black hens on the top of the magic quoted above?
> I don't care about X on this system, all that much, honestly.
"Technicolor" thingy seems to be side effect of your particular
graphics card, no?
Michal
next prev parent reply other threads:[~2001-02-15 20:48 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
2001-02-15 20:15 ` John Jasen
2001-02-15 20:47 ` Michal Jaegermann [this message]
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=20010215134747.A13942@ellpspace.math.ualberta.ca \
--to=michal@ellpspace.math.ualberta.ca \
--cc=andre@linux-ide.org \
--cc=axp-list@redhat.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