On 03/28/2017 05:06 PM, Rafael J. Wysocki wrote:
On Tue, Mar 28, 2017 at 10:01 PM, Corey Minyard wrote:
On 03/25/2017 09:08 AM, Sinan Kaya wrote:
On 3/24/2017 10:55 PM, Corey Minyard wrote:
Why would a timeout for a message be expected? The BMC should
at least respond with an error for an in
On Tue, Mar 28, 2017 at 10:01 PM, Corey Minyard wrote:
> On 03/25/2017 09:08 AM, Sinan Kaya wrote:
>>
>> On 3/24/2017 10:55 PM, Corey Minyard wrote:
>>>
>>> Why would a timeout for a message be expected? The BMC should
>>> at least respond with an error for an incorrect message.
>>
>> Let me add
On 03/25/2017 09:08 AM, Sinan Kaya wrote:
On 3/24/2017 10:55 PM, Corey Minyard wrote:
Why would a timeout for a message be expected? The BMC should
at least respond with an error for an incorrect message.
Let me add some more context...
In this particular case, the FRU ID that I was trying to
On 3/24/2017 10:55 PM, Corey Minyard wrote:
> Why would a timeout for a message be expected? The BMC should
> at least respond with an error for an incorrect message.
Let me add some more context...
In this particular case, the FRU ID that I was trying to access was
correct.
Platform supports
Why would a timeout for a message be expected? The BMC should
at least respond with an error for an incorrect message.
-corey
On 03/23/2017 10:32 AM, Sinan Kaya wrote:
Getting timeout message from BMC when trying to read from a non-existent
FRU. This is expected but warning is not.
Let's redu
Getting timeout message from BMC when trying to read from a non-existent
FRU. This is expected but warning is not.
Let's reduce the warning to debug.
Signed-off-by: Sinan Kaya
---
drivers/acpi/acpi_ipmi.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/acpi/acpi_ip
6 matches
Mail list logo