On 03/22/2016 12:56 AM, Eli Cohen wrote:
On Mon, Mar 21, 2016 at 04:02:16PM +1100, Alexey Kardashevskiy wrote:
After more tries, I found that if for whatever reason mlx4_core
fails to stop while shutting the guest down (last message is
"mlx4_core 0000:00:00.0: mlx4_shutdown was called"), then next time
VF in guest won't start.
Example #1:
mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
mlx4_core: Initializing 0000:00:00.0
mlx4_core 0000:00:00.0: enabling device (0000 -> 0002)
mlx4_core 0000:00:00.0: Detected virtual function - running in slave mode
mlx4_core 0000:00:00.0: Sending reset
mlx4_core 0000:00:00.0: Sending vhcr0
mlx4_core 0000:00:00.0: HCA minimum page size:1
mlx4_core 0000:00:00.0: UAR size:4096 != kernel PAGE_SIZE of 65536
mlx4_core 0000:00:00.0: Failed to obtain slave caps
Alexey, can you verify that the value of the enable_4k_uar parameter
is false?
aik@fstn1-p1:~$ cat
/sys/bus/pci/drivers/mlx4_core/module/parameters/enable_4k_uar
N
aik@fstn1-p1:~$
Example #2:
root@le-dbg:~# dhclient eth0
NETDEV WATCHDOG: eth0 (mlx4_core): transmit queue 11 timed out
------------[ cut here ]------------
WARNING: at /home/aik/p/guest-kernel/net/sched/sch_generic.c:303
and no IP assigned, timed out.
This is fixed by the guest restart, first restart might not help,
then the second restart will.
The host is running the latest upstream plus the patch I am replying
to. The guest is using initramdisk from debian bootstrap and vanilla
v4.2 kernel, ppc64le arch, POWER8 chip, QEMU is running with 1 CPU
and 2GB of RAM.
Does this look any familiar?
This is completely unrelated to the compatibility problem you reported
and which this patch addresses. We will reproduce in house and post a
fix.
Example #2 is but example #1 mentions "UAR size" :)
--
Alexey
