From: James Bottomley <James.Bottomley@SteelEye.com>
To: Michael Joosten <michael.joosten@c-lab.de>
Cc: Michael Reed <mdr@sgi.com>, pazke@donpac.ru, linux-scsi@vger.kernel.org
Subject: Re: [PATCH]: Re: qla1280.c broken on SGI visws, PCI coherency problem
Date: Wed, 14 Dec 2005 09:29:16 -0800 [thread overview]
Message-ID: <1134581356.3278.1.camel@mulgrave> (raw)
In-Reply-To: <439FA708.9070508@c-lab.de>
On Wed, 2005-12-14 at 06:00 +0100, Michael Joosten wrote:
> >Perhaps Mr. Joosten can confirm his failing case with the UP kernel?
> >
> >
> >
> OK, I'm currently doing this, though with a Fedora Core3 kernel
> (2.6.12-1.1381-FC3) UP and SMP, running it with some ooold filesystem
> benchmark on a similarly old PIII 500MHz board. What else is possible is
> an Intel dual PII (450MHz) server board (N440BX) , a dual PIII(730MHz)
> workstation and a very recent one with hyperthreading PIV. I'm currently
> using a distributed kernel with modules, because this version still has
> the mmiowb() in place (I hope!) .
> There might be a timing issue (the faults happend somehow earlier once
> the board and the VisWS got warmer), but I hope that the other platforms
> will show a little difference...
> Well, the PIII board with both a 550 and a 800 MHz proc showed no
> difference, the driver just *works*, no failure in 20 runs. It looks
> like the problem only shows up in the VISWS. Perhaps I try it again
> putting the QLA1080 in the 32bit slot, which is apparently not
> controlled by the Lithium, but rather a plain PIIX chip. And perhaps
> some other platform and chipset.
Yes, the PIO posting issue is VISWS only, I think. Could you confirm
that your original bug report was on a SMP VISWS, and could you try the
tests over using a UP kernel on the VISWS?
Thanks,
James
next prev parent reply other threads:[~2005-12-14 17:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 19:11 qla1280.c broken on SGI visws, PCI coherency problem Michael Joosten
2005-12-09 23:48 ` Michael Reed
2005-12-12 21:00 ` [PATCH]: " Michael Reed
2005-12-12 21:24 ` Christoph Hellwig
2005-12-12 21:31 ` Jesse Barnes
2005-12-12 21:47 ` James Bottomley
2005-12-12 23:00 ` Michael Reed
2005-12-13 13:22 ` Michael Reed
2005-12-13 14:50 ` James Bottomley
2005-12-13 18:15 ` Michael Reed
2005-12-14 5:00 ` Michael Joosten
2005-12-14 17:29 ` James Bottomley [this message]
2005-12-15 1:17 ` Michael Joosten
2005-12-15 2:20 ` Jeremy Higdon
2005-12-15 16:21 ` Michael Joosten
2005-12-14 1:39 ` Jeremy Higdon
2005-12-14 3:16 ` Michael Reed
2005-12-14 1:28 ` Jeremy Higdon
2005-12-14 4:59 ` James Bottomley
2005-12-14 23:56 ` Jeremy Higdon
2005-12-15 0:14 ` Michael Reed
2005-12-15 1:13 ` Jeremy Higdon
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=1134581356.3278.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.com \
--cc=michael.joosten@c-lab.de \
--cc=pazke@donpac.ru \
/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.