Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Sep 2011 14:22:59 +0200
From:      Thomas Vogt <freebsdlists@bsdunix.ch>
To:        Marius Strobl <marius@alchemy.franken.de>
Cc:        stable@freebsd.org
Subject:   Re: mpt0 timeouts with an intel SASUC8I controller
Message-ID:  <2843DCCD-4813-4B3A-B46E-0F73D87A1E3E@bsdunix.ch>
In-Reply-To: <20110919195340.GQ40781@alchemy.franken.de>
References:  <94E5E0D6-3062-44A2-8ED3-3C3D44FA7A09@bsdunix.ch> <20110919190659.GA76654@alchemy.franken.de> <B1BE548E-5EEE-4B04-8DD3-5D16F1600E7C@bsdunix.ch> <20110919195340.GQ40781@alchemy.franken.de>

next in thread | previous in thread | raw e-mail | index | archive | help


On Sep 19, 2011, at 9:53 PM, Marius Strobl wrote:

> 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.

I already use the latest IR firmware on my controller. This Intel SASUC8I supports both initiator target (IT) and integrated RAID (IR) firmware as most LSI SAS host adapter [1]. I flashed the controller from IR to IT. It works now. 


With IR firmware:
mptutil show adapter
mpt0 Adapter:
      Board Name: SASUC8I
  Board Assembly: L3-25071-00C
       Chip Name: C1068E
   Chip Revision: UNUSED
     RAID Levels: RAID0, RAID1, RAID1E
   RAID0 Stripes: 64k
  RAID1E Stripes: 64k
RAID0 Drives/Vol: 2-10
RAID1 Drives/Vol: 2


With IT firmware:
mptutil show adapter
mpt0 Adapter:
       Board Name: SASUC8I
   Board Assembly: L3-25071-00C
        Chip Name: C1068E
    Chip Revision: UNUSED
      RAID Levels: none


[1] http://kb.lsi.com/KnowledgebaseArticle16266.aspx

Regards,
Thomas


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2843DCCD-4813-4B3A-B46E-0F73D87A1E3E>