public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Berkley Shands <berkley@cs.wustl.edu>
Cc: gibbs@scsiguy.com, Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	pbadari@us.ibm.com
Subject: Re: x86_64 + 2.6.1-rc3 panics on aic79xx
Date: 08 Jan 2004 12:26:07 -0500	[thread overview]
Message-ID: <1073582767.2741.14.camel@mulgrave> (raw)
In-Reply-To: <200401081627.i08GRgZ0000027670@mudpuddle.cs.wustl.edu>

On Thu, 2004-01-08 at 11:27, Berkley Shands wrote:
> 	A pure stock 2.6.1-rc3 kernel also bug halts with sg corruption
> on the first scsi retry. It seems that the iommu has serious issues
> with all three variants of  current kernel patches.

Andi Kleen has produced a patch for the sg list problems.  Could you see
if you can reproduce the issues when Andi produces a patch kit for
x86_64 and -rc3, so we're not trying to debug non-scsi issues?

Thanks,

James

      reply	other threads:[~2004-01-08 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 16:27 x86_64 + 2.6.1-rc3 panics on aic79xx Berkley Shands
2004-01-08 17:26 ` James Bottomley [this message]

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=1073582767.2741.14.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=berkley@cs.wustl.edu \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbadari@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