From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Saeed Mahameed <saeedm@dev.mellanox.co.il>,
Joao Pinto <Joao.Pinto@synopsys.com>
Cc: Saeed Mahameed <saeedm@mellanox.com>, netdev <netdev@vger.kernel.org>
Subject: Re: mlx5 endpoint driver problem
Date: Tue, 9 May 2017 18:38:04 +0100 [thread overview]
Message-ID: <1ea4f8fa-16dc-01d8-2995-514053635fd3@synopsys.com> (raw)
In-Reply-To: <CALzJLG8uieD52haz2WYbh2zWLKLgF-kUFw-2DU-sqC1+byPAKw@mail.gmail.com>
Hi Saeed,
Às 6:35 PM de 5/9/2017, Saeed Mahameed escreveu:
> On Tue, May 9, 2017 at 7:25 PM, Joao Pinto <Joao.Pinto@synopsys.com> wrote:
>> Hello,
>>
>> I am making tests with a Mellanox MLX5 Endpoint, and I am getting kernel hangs
>> when trying to enable the hca:
>>
>> mlx5_core 0000:01:00.0: enabling device (0000 -> 0002)
>> mlx5_core 0000:01:00.0: Warning: couldn't set 64-bit PCI DMA mask
>> mlx5_core 0000:01:00.0: Warning: couldn't set 64-bit consistent PCI DMA mask
>> mlx5_core 0000:01:00.0: firmware version: 16.19.21102
>> INFO: task swapper:1 blocked for more than 10 seconds.
>> Not tainted 4.11.0-BETAMSIX1 #51
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> swapper D 0 1 0 0x00000000
>>
>> Stack Trace:
>> __switch_to+0x0/0x94
>> __schedule+0x1da/0x8b0
>> schedule+0x26/0x6c
>> schedule_timeout+0x2da/0x380
>> wait_for_completion+0x92/0x104
>> mlx5_cmd_exec+0x70e/0xd60
>> mlx5_load_one+0x1b4/0xad8
>> init_one+0x404/0x600
>> pci_device_probe+0x122/0x1f0
>> really_probe+0x1ac/0x348
>> __driver_attach+0xa8/0xd0
>> bus_for_each_dev+0x3c/0x74
>> bus_add_driver+0xc2/0x184
>> driver_register+0x50/0xec
>> init+0x40/0x60
>>
>> (...)
>>
>> Stack Trace:
>> __switch_to+0x0/0x94
>> __schedule+0x1da/0x8b0
>> schedule+0x26/0x6c
>> schedule_timeout+0x2da/0x380
>> wait_for_completion+0x92/0x104
>> mlx5_cmd_exec+0x70e/0xd60
>> mlx5_load_one+0x1b4/0xad8
>> init_one+0x404/0x600
>> pci_device_probe+0x122/0x1f0
>> really_probe+0x1ac/0x348
>> __driver_attach+0xa8/0xd0
>> bus_for_each_dev+0x3c/0x74
>> bus_add_driver+0xc2/0x184
>> driver_register+0x50/0xec
>> init+0x40/0x60
>> mlx5_core 0000:01:00.0: wait_func:882:(pid 1): ENABLE_HCA(0x104) timeout. Will
>> cause a leak of a command resource
>> mlx5_core 0000:01:00.0: enable hca failed
>> mlx5_core 0000:01:00.0: mlx5_load_one failed with error code -110
>> mlx5_core: probe of 0000:01:00.0 failed with error -110
>>
>> Could you give me a clue of what might be happennig?
>>
>
> Hi Joao,
>
> Looks like FW is not responding, most likely due to the DMA mask
> setting warnings, which architecture is this ?
>
>> Thanks,
>> Joao
I am working with a 32-bit ARC processor based board, connected to a prototyped
Gen4 PCI RC.
Thanks,
Joao
next prev parent reply other threads:[~2017-05-09 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 16:25 mlx5 endpoint driver problem Joao Pinto
2017-05-09 17:35 ` Saeed Mahameed
2017-05-09 17:38 ` Joao Pinto [this message]
2017-05-09 17:44 ` Saeed Mahameed
2017-05-09 17:57 ` Joao Pinto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ea4f8fa-16dc-01d8-2995-514053635fd3@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox