From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tom Rini <tmrini@ntplx.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: SCSI crashes with vger
Date: Fri, 19 Mar 1999 18:12:31 +0100 [thread overview]
Message-ID: <19990319181231.022598@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.05.9903181816420.8817-100000@p05-10.hartford.dialin.ntplx.com>
On Thu, Mar 18, 1999, Tom Rini <tmrini@ntplx.net> wrote:
>The patch that "fixed" things before was incorrect and added in some
>cli()s i think. The actual fix shouldn't be too hard to yank out of
>patch-2.2.2, on any of the kernel.org mirrors.
I didn't find any patch in the scsi code that looks like what you
describe in 2.2.2 and 2.2.3 patches on kernel.org, but the fix may have
been elsewhere...
As far as I know, the problem is a page fault in the interrupt handler of
the NCR driver, when completing a request. I'm not familiar enough with
both the scsi subsystem and linux vm to conclude anything from that, but
I'm still trying to figure out what's happening. Some help (directions to
look into) would be welcome, I'll post a more detailed report of what I
found until now later today.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-19 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-18 17:31 SCSI crashes with vger Benjamin Herrenschmidt
1999-03-18 22:55 ` Tom Rini
1999-03-18 23:07 ` Benjamin Herrenschmidt
1999-03-18 23:18 ` Tom Rini
1999-03-19 17:12 ` Benjamin Herrenschmidt [this message]
1999-03-19 20:32 ` Tom Rini
1999-03-19 20:41 ` Benjamin Herrenschmidt
1999-03-21 0:42 ` Douglas Godfrey
1999-03-21 5:28 ` Matroxfb, PReP, and ioremap Troy Benjegerdes
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=19990319181231.022598@mail.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tmrini@ntplx.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;
as well as URLs for NNTP newsgroup(s).