[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4E6FB501.9020608@canonical.com>
Date: Tue, 13 Sep 2011 13:54:41 -0600
From: Tim Gardner <tim.gardner@...onical.com>
To: "Williams, Dan J" <dan.j.williams@...el.com>
CC: edmund.nadolski@...el.com, dave.jiang@...el.com,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH] isci: Make warning messages unique
On 09/13/2011 01:38 PM, Williams, Dan J wrote:
> On Mon, Sep 12, 2011 at 1:46 PM, Tim Gardner<tim.gardner@...onical.com> wrote:
>> Hi,
>>
>> I've got a 2-way Sandybridge server with an 'Intel(R) C600 SAS Controller'.
>> The driver makes a boatload of dmesg noise with non-unique messages
>> distinguished only by the event code. For example, I've got 296 of these in
>> dmesg:
>>
>> (NULL device *): sci_phy_event_handler:735: PHY starting substate machine
>> received unexpected event_code b3402000
>>
>> In an effort to discover which of the 9 places from which this message was
>> emitted I added a line number.
>>
>> The next step is to decide if all of these really need to be dev_warn().
>
> Can you describe your storage layout? I'd like to move these to
> dev_dbg() but I want to verify that the reports are benign.
>
Its a couple of 500GB Western Digital SATA drives (I think) in SAS bays.
Not sure what the boot drive is. See attached dmesg.
rtg
--
Tim Gardner tim.gardner@...onical.com
View attachment "dmesg.txt" of type "text/plain" (134905 bytes)
Powered by blists - more mailing lists