> On Mar 6, 2016, at 10:04 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
>
>>
>>> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>>>
>>> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
>>>
Hi,
The message is
On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
>
> > On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
> >
> > On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
> >
> >> Hi,
> >>
> >> The message is harmless, it's a reminder that you should tune the kernel
> >> for
> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
>
>> Hi,
>>
>> The message is harmless, it's a reminder that you should tune the kernel for
>> your workload. When the message is triggered, it means that a potential
>> c
On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
> Hi,
>
> The message is harmless, it's a reminder that you should tune the kernel for
> your workload. When the message is triggered, it means that a potential
> command was deferred, likely for only a few microseconds, and then ever
Hi,
The message is harmless, it's a reminder that you should tune the kernel for
your workload. When the message is triggered, it means that a potential
command was deferred, likely for only a few microseconds, and then everything
moved on as normal.
A command uses anywhere from 0 to a few
I am use 10-STABLE r295539 and LSI SAS2008.
mps0: port 0x8000-0x80ff mem
0xdfc0-0xdfc03fff,0xdfb8-0xdfbb irq 32 at device 0.0 on pci2
mps0: Firmware: 15.00.00.00, Driver: 20.00.00.00-fbsd
mps0: IOCCapabilities: 185c
mps1: port 0x7000-0x70ff mem
0xdf60-0xdf603fff,0xdf58-0xdf
