mpt0 timeouts with an intel SASUC8I controller

[Marius Strobl]

On Mon, Sep 19, 2011 at 09:13:53PM +0200, Thomas Vogt wrote:
> Hi Marius
> 
> On 19.09.2011, at 21:06, Marius Strobl wrote:
> 
> > On Mon, Sep 19, 2011 at 02:45:04PM +0200, Thomas Vogt wrote:
> >> Hello
> >> 
> >> I've stability issue with my new intel SASUC8I [1] PCIe controller. It's a LSI 1068e based controller. After a few minutes with disk io (csup or scrub by example) my FreeBSD 8-stable (64bit) is "freezing" for a couple of minutes and I see a lot of error messages like:
> >> 
> >> Sep 17 03:10:03 gw kernel: mpt0: request 0xffffff80002bc3b0:48367 timed out for ccb 0xffffff00050a8000 (req->ccb 0xffffff00050a8000)
> >> Sep 17 03:10:03 gw kernel: mpt0: request 0xffffff80002bbb40:48368 timed out for ccb 0xffffff0004f81800 (req->ccb 0xffffff0004f81800)
> >> Sep 17 03:10:03 gw kernel: mpt0: completing timedout/aborted req 0xffffff80002bc3b0:48367
> >> Sep 17 03:10:03 gw kernel: mpt0: completing timedout/aborted req 0xffffff80002bbb40:48368
> >> Sep 17 03:10:03 gw kernel: mpt0: Timedout requests already complete. Interrupts may not be functioning
> >> 
> > 
> > If this really is an issue with interrupts not getting delivered you
> > could try whether disabling MSI/MSI-X by setting hw.pci.enable_msi=0
> > and hw.pci.enable_msix=0 either on the loader prompt or via loader.conf
> > works around it.
> 
> I already tried this. It didn't change anything. Same timeouts.
> 
> I also tried vfs.zfs.vdev.min_pending="1" and vfs.zfs.vdev.max_pending="1" in loader.conf without any positive change.
> 

Okay, I was just worried as I recently changed mpt(4) to use MSI/MSI-X
by default for the SAS variants but couldn't test with all of them. I'm
not aware of any issues with the driver causing command timeouts though.
I'd make sure that both the controller and the disks have the latest
firmware; IIRC some time ago someone reported on current@ that updating
the firmware of the disks solved the timeouts he was seeing for him.

Marius