The working system is running: Linux dracosan 3.5.0-26-generic
#42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 x86_64 x86_64
GNU/Linux
With that said, the hardware is substantially different between the
two, in the working system I'm using a QLE2462 (I thought it was a
QLA2462 but I just confirmed it's not).
Working storage: Arima NM461 board, dual opteron 2214HE, 8x 1GB RAM,
QLE2462 HBA, LSI 8888ELP SAS RAID card, Kernel 3.5.0-26 (Ubuntu FUBAR)
Crashy storage #1: IBM HS21 (8853) blade, dual Xeon 5148, 4x 1GB RAM,
2x QLA2462 HBA, 4x 1GB RAM, ServeRaid 8k SAS RAID card, IBM BSE3
expander, Kernel 3.19.3-200 (Fedora 21)
Crashy storage #2: IBM HS21 (8853) blade, dual Xeon 5148, 4x 1GB RAM,
1x QLA2462 HBA, 4x 1GB RAM, LSI 1064E SAS card, Kernel 4.0.0.rc2
(Fedora 22) (Server was built just for testing)
I have a friend running a QLA2462 (PCI-X) in a PowerEdge 2850
successfully, he's going to check it later and see what kernel he's
on, all he could remember is that it's Ubuntu.
^^
Thanks!
Dan
On Tue, Apr 7, 2015 at 5:08 PM, Nicholas A. Bellinger
<nab@xxxxxxxxxxxxxxx> wrote:
> On Mon, 2015-04-06 at 23:33 -0700, Christoph Hellwig wrote:
>> Hi Dan,
>>
>> it seems like the MISCOMPARE case of COMPARE AND WRITE has been broken
>> for quite a while.
>>
>> See my post from March 30 ("hang during COMPARE AND SWAP", which shows a
>> similar issues using a synthetic test suite.
>
> Not exactly. The one you reported earlier is a bug specific to loopback
> and vhost with COMPARE_AND_WRITE, and AFAICT has always been broken.
> I'm working on a patch for that now..
>
> From what I can gather from Dan's log with qla2xxx, a MISCOMPARE occurs
> in compare_and_write_callback(), followed up by an ABORT_TASK. This is
> not what's happening with loopback.
>
> Dan, can you confirm which kernel version you where previously using
> qla2xxx target mode with Ubuntu 11.04..?
>
> Thanks,
>
> --nab
>
>
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
