All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org, Tarte@us.ibm.com,
	Robert <Robert_Tarte@adaptec.com>,
	Jeff Garzik <jgarzik@redhat.com>
Subject: Re: [PATCH] aic94xx: driver assertion in non-x86 BIOS env
Date: Tue, 21 Feb 2006 22:26:02 -0800	[thread overview]
Message-ID: <20060222062602.GA30870@us.ibm.com> (raw)
In-Reply-To: <1140549399.3215.20.camel@mulgrave.il.steeleye.com>

James Bottomley <James.Bottomley@SteelEye.com> wrote:
> Actually, it's still not quite working for me.  This is what I get from
> 2.6.16-rc4 with the Jeff Garzik SAS tree (which has this fix applied).
> The soft lockup basically means it was hung in asd_read_ocm():

ok, looking into this. Is the soft lockup detect in the same
(asd_read_ocm+0x120) function and offset. I did a resync with Jeff's tree
and ran the code on a ppc64 system. This ran ok. I will move my card to an
IA64 tomorrow to see if I can recreate (which may be unlikely as it ran a
number of loads before) and also generate a .lst file.

-andmike
--
Michael Anderson
andmike@us.ibm.com

  reply	other threads:[~2006-02-22  6:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17  2:36 [PATCH] aic94xx: driver assertion in non-x86 BIOS env Mike Anderson
2006-02-20 11:11 ` Jeff Garzik
2006-02-21 19:16 ` James Bottomley
2006-02-22  6:26   ` Mike Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-22 21:24 Tarte, Robert
2006-02-22 21:36 ` James Bottomley
2006-03-01 20:22 ` Jeff Garzik
2006-03-01 20:57 Tarte, Robert
2006-03-01 21:12 ` Matthew Wilcox
2006-03-01 21:25 ` James Bottomley
2006-03-02 14:45 ` James Bottomley
2006-03-01 21:22 Tarte, Robert
2006-03-01 21:39 ` Jeff Garzik

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=20060222062602.GA30870@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Robert_Tarte@adaptec.com \
    --cc=Tarte@us.ibm.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    /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.