All of lore.kernel.org
 help / color / mirror / Atom feed
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 21:41:02 +0100	[thread overview]
Message-ID: <19990319214102.000691@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.05.9903191529140.14954-100000@p05-10.hartford.dialin.ntplx.com>


On Fri, Mar 19, 1999, Tom Rini <tmrini@ntplx.net> wrote:

>Er, I guess I wasn't too clear.  The wrong patch looked nothing like the
>right patch. :)  The "right" patch was the generic scsi fix listed in the
>2.2.2 rel notes, not sure what files tho.  However in skimming the 2.2.2
>patch I saw some changes to linux/drivers/scsi/ncr53c8xx.c.  reversing
>this had no effect I take it? (didn't look at the full context of where
>the diff went, might not effect us at all..)

I saw them but I didn't find them related to the problem. I may have been
wrong in my jugement however, I'll give this a closer look. I havent seen
any related fix to the SCSI generic code (only in some drivers),
apparently anything that looks like related to this bug. I may have
missed something and I'll look more closely.

Apparently, adding a save_flags()/cli()/restore_flags() in the
ncr_complete() function makes the code go a little bit further (to just
after the restore_flags() in my first test). I'm still moving the
restore_flag around to find out what is the exact critical region, but my
first impression is that part of the request structure itself (the
structure or some associated stuff) is beeing deallocated by another
interrupt. I still have to determine if another ncr interrupt happens at
this point or if it's something eventually coming from the MESH driver.


-- 
           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.   ]]

  reply	other threads:[~1999-03-19 20:41 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
1999-03-19 20:32         ` Tom Rini
1999-03-19 20:41           ` Benjamin Herrenschmidt [this message]
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=19990319214102.000691@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 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.