public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: mikeand@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Broken SCSI code in the BK tree (was: 2.5.59-mm8)
Date: 06 Feb 2003 17:25:25 -0600	[thread overview]
Message-ID: <1044573927.2332.100.camel@mulgrave> (raw)
In-Reply-To: <275930000.1044570608@[10.10.2.4]>

On Thu, 2003-02-06 at 16:30, Martin J. Bligh wrote:
> > OK, I threw a little bit of debug in there:
> > I'd show you the code, except it just ate my root filesystem.
> > Likelihood of me doing further research is thus small.
> 
> 
> Hmmmm .... did a disassemble of this on a similar machine (see end of email)
> data seems to contradict what I was looking at previously ....
> not sure what happened, but this set makes much more sense,
> as it leads to 13c in the offset ;-)
> 
> 0xc01c1ac6 <isp1020_intr_handler+486>:  mov    %eax,0x13c(%ebp)
> which is drivers/scsi/qlogicisp.c:1051
> 
> Cmnd->result = isp1020_return_status(sts);
> 
> seemingly Cmnd is null ... this is in 
[...]

That looks more like it.

My guess is that the command slot was emptied previously, but I don't
understand enough about the mailbox specifics of the isp1020 to be sure.

Can you try adding

if(!Cmnd) {
	printk(KERN_ERR "isp1020 Cmnd is NULL for slot %d, out_ptr %d\n",
cmd_slot, out_ptr);
	continue;
}

Just below the Cmnd = hostdata->cmd_slots[cmd_slot];

> say for sure (if this wasn't related to some SCSI subsystem change, 
> can I just revert out this section?)

No, I'm afraid not.  That was just the elimination of those fields from
Scsi_Cmnd so now it has to be indirect through cmnd->device.  It won't
compile without this.

James



  reply	other threads:[~2003-02-06 23:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  7:31 2.5.59-mm8 Andrew Morton
2003-02-04  8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04  8:05   ` 2.5.59-mm8 Andrew Morton
2003-02-04  8:08     ` 2.5.59-mm8 Joshua Kwan
2003-02-04  8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04  8:17   ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15     ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06  5:13       ` Martin J. Bligh
2003-02-06 20:50         ` Martin J. Bligh
2003-02-06 22:30           ` Martin J. Bligh
2003-02-06 23:25             ` James Bottomley [this message]
2003-02-07  1:24               ` Patrick Mansfield
2003-02-07  2:01                 ` Martin J. Bligh
2003-02-07  2:25                   ` Patrick Mansfield
2003-02-07  4:05                     ` Doug Ledford
2003-02-07  4:19                       ` Anton Blanchard
2003-02-07  8:50                         ` Mike Anderson
2003-02-07  4:19                       ` Andrew Morton
2003-02-07  4:24                         ` Doug Ledford
2003-02-07  4:35                           ` William Lee Irwin III
2003-02-07  4:53                             ` Matthew Jacob
2003-02-07  4:50                         ` Matthew Jacob
2003-02-07  4:28                       ` Martin J. Bligh
2003-02-04  9:07   ` 2.5.59-mm8 Dave Hansen
2003-02-04  9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04  9:21   ` Andrew Morton
2003-02-04  9:29     ` David S. Miller
2003-02-04  9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05  8:08 ` 2.5.59-mm8 Mike Galbraith

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=1044573927.2332.100.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mikeand@us.ibm.com \
    /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