From: Miles Lane <miles@megapathdsl.net>
To: JP Navarro <navarro@mcs.anl.gov>
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 13:36:58 -0800 [thread overview]
Message-ID: <3A5B847A.3010200@megapathdsl.net> (raw)
In-Reply-To: <OF0CDA4866.9019CFB7-ON852569CF.006D12FC@lotus.com> <3A5B7DB3.F29D02CE@mcs.anl.gov>
JP Navarro wrote:
> One possibility:
>
> When we first tested 2.4.0-test8 on NetFinity 7000s we had random crashes,
> typically within an hour of booting. The problem was identified as a Wiseman
> Systems Management adapter generated hardware interrupt that 2.4 doesn't handle
> (this was not a problem with 2.2.x).
>
> If you have these adapters installed, remove them.
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?
If you have detailed information about the interrupt problem,
perhaps you could send it to the list and see if a fix is possible.
Miles
-
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 21:38 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 [this message]
2001-01-09 22:22 ` JP Navarro
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=3A5B847A.3010200@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=kenbo@iris.com \
--cc=linux-kernel@vger.kernel.org \
--cc=navarro@mcs.anl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.