From: JP Navarro <navarro@mcs.anl.gov>
To: Miles Lane <miles@megapathdsl.net>
Cc: Ken Brunsen/Iris <kenbo@iris.com>, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.0 scsi problems on NetFinity servers
Date: Tue, 09 Jan 2001 16:22:44 -0600 [thread overview]
Message-ID: <3A5B8F34.125231D4@mcs.anl.gov> (raw)
In-Reply-To: <OF0CDA4866.9019CFB7-ON852569CF.006D12FC@lotus.com> <3A5B7DB3.F29D02CE@mcs.anl.gov> <3A5B847A.3010200@megapathdsl.net>
Miles Lane wrote:
...
> Are you saying that this is a hardware bug that is impossible to
> develop a work-around for in the kernel? If this is just a bug,
> shouldn't we try to fix it rather than avoid it?
This is hardware behaving as designed but not supported by the kernel. IBM was
aware of the problem and working on a solution. Since the offending hardware is
a PCI card that is useless under Linux. The simple solution is to remove it.
If IBM wants these cards to work with Linux they should do a lot more than
supply patches that keep the kernel from crashing. At a minimum, publish specs
so someone else can patch the kernel and write drivers to make full use of the
card's features under Linux. We're still hoping.
> If you have detailed information about the interrupt problem,
> perhaps you could send it to the list and see if a fix is possible.
Wish I could have. Our machines would totally freeze.
JP Navarro
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 20:50 linux-2.4.0 scsi problems on NetFinity servers Ken Brunsen/Iris
2001-01-09 21:08 ` JP Navarro
2001-01-09 21:36 ` Miles Lane
2001-01-09 22:22 ` JP Navarro [this message]
2001-01-10 20:49 ` Tim Wright
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 21:27 Ken Brunsen/Iris
2001-01-10 13:58 Ken Brunsen/Iris
2001-01-11 13:54 kenbo
2001-01-11 20:00 kenbo
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=3A5B8F34.125231D4@mcs.anl.gov \
--to=navarro@mcs.anl.gov \
--cc=kenbo@iris.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
/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