From: Dennis Stosberg <dennis@stosberg.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre7-ac2: Promise Ultra100TX2 broken
Date: Fri, 26 Apr 2002 19:56:12 +0200 [thread overview]
Message-ID: <20020426175612.GA559@leonov.stosberg.net> (raw)
Hello,
In the late 2.4.19-preX-acY the support for the Promise
Ultra100TX2 is broken. This problem was already reported on
lkml and on the German SuSE Linux mailing list. According to
information from that list the problem only affects the
Ultra100TX2, but NOT the Ultra100TX.
The latest -ac kernel I know to work with this controller, is
2.4.19-pre2-ac4. I just tried 2.4.19-pre7-ac2: it
fails. 2.4.19-pre4-ac3 has also been reported to fail:
http://www.ussg.iu.edu/hypermail/linux/kernel/0203.3/1011.html
At boot time 2.4.19-pre7-ac2 prints these error messages. The
drives ARE conntected using an 80-pin cable:
hde: set_drive_speed_status: status=0xff { Busy }
Warning: Primary channel requires an 80-pin cable for operation.
hde reduced to Ultra33 mode.
[..]
end_request: I/O error, dev 21:00 (hde), sector 0
end_request: I/O error, dev 21:00 (hde), sector 2
end_request: I/O error, dev 21:00 (hde), sector 4
end_request: I/O error, dev 21:00 (hde), sector 6
end_request: I/O error, dev 21:00 (hde), sector 0
end_request: I/O error, dev 21:00 (hde), sector 2
end_request: I/O error, dev 21:00 (hde), sector 4
end_request: I/O error, dev 21:00 (hde), sector 6
You can find the configuration of the failing kernel at:
http://stosberg.net/tmp/config-2.4.19-pre7-ac2
Currently I'm using 2.4.19-pre5aa1 without problems.
Regards,
Dennis
--
Dennis Stosberg
eMail: dennis@stosberg.net
dstosber@techfak.uni-bielefeld.de
pgp key: http://stosberg.net/dennis.asc
next reply other threads:[~2002-04-26 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 17:56 Dennis Stosberg [this message]
2002-04-26 19:42 tomas szepe
2002-04-26 21:55 ` Dennis Stosberg
2002-04-27 11:02 ` tomas szepe
2002-04-27 14:22 ` Dennis Stosberg
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=20020426175612.GA559@leonov.stosberg.net \
--to=dennis@stosberg.net \
--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
all inboxes | Powered by JetHome®