Displaying 7 results from an estimated 7 matches for "en_dbg".
2019 Dec 10
0
[PATCH net-next v10 2/3] mlx4: use new txqueue timeout argument
...t;qpn, tx_ring->sp_cqn,
- tx_ring->cons, tx_ring->prod);
- }
+ en_warn(priv, "TX timeout on queue: %d, QP: 0x%x, CQ: 0x%x, Cons: 0x%x, Prod: 0x%x\n",
+ txqueue, tx_ring->qpn, tx_ring->sp_cqn,
+ tx_ring->cons, tx_ring->prod);
priv->port_stats.tx_timeout++;
en_dbg(DRV, priv, "Scheduling watchdog\n");
--
MST
2019 Dec 10
0
[PATCH net-next v10 2/3] mlx4: use new txqueue timeout argument
...t;qpn, tx_ring->sp_cqn,
- tx_ring->cons, tx_ring->prod);
- }
+ en_warn(priv, "TX timeout on queue: %d, QP: 0x%x, CQ: 0x%x, Cons: 0x%x, Prod: 0x%x\n",
+ txqueue, tx_ring->qpn, tx_ring->sp_cqn,
+ tx_ring->cons, tx_ring->prod);
priv->port_stats.tx_timeout++;
en_dbg(DRV, priv, "Scheduling watchdog\n");
--
MST
2019 Dec 03
0
[vhost:linux-next 4/11] drivers/net/ethernet/mellanox/mlx4/en_netdev.c:1376:12: error: 'tx_ring' undeclared; did you mean 'en_print'?
...n", priv->port);
1374
1375 en_warn(priv, "TX timeout on queue: %d, QP: 0x%x, CQ: 0x%x, Cons: 0x%x, Prod: 0x%x\n",
> 1376 txqueue, tx_ring->qpn, tx_ring->sp_cqn,
1377 tx_ring->cons, tx_ring->prod);
1378
1379 priv->port_stats.tx_timeout++;
1380 en_dbg(DRV, priv, "Scheduling watchdog\n");
1381 queue_work(mdev->workqueue, &priv->watchdog_task);
1382 }
1383
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all at lists.01.org Intel Corporation...
2019 Dec 03
4
[PATCH RFC net-next v8 0/3] netdev: ndo_tx_timeout cleanup
A bunch of drivers want to know which tx queue triggered a timeout,
and virtio wants to do the same.
We actually have the info to hand, let's just pass it on to drivers.
Note: tested with an experimental virtio patch by Julio.
That patch itself isn't ready yet though, so not included.
Other drivers compiled only.
Michael S. Tsirkin (3):
netdev: pass the stuck queue to the timeout
2019 Dec 10
4
[PATCH net-next v11 0/3] netdev: ndo_tx_timeout cleanup
Sorry about the churn, v10 was based on net - not on net-next
by mistake.
A bunch of drivers want to know which tx queue triggered a timeout,
and virtio wants to do the same.
We actually have the info to hand, let's just pass it on to drivers.
Note: tested with an experimental virtio patch by Julio.
That patch itself isn't ready yet though, so not included.
Other drivers compiled only.
2019 Dec 10
4
[PATCH net-next v11 0/3] netdev: ndo_tx_timeout cleanup
Sorry about the churn, v10 was based on net - not on net-next
by mistake.
A bunch of drivers want to know which tx queue triggered a timeout,
and virtio wants to do the same.
We actually have the info to hand, let's just pass it on to drivers.
Note: tested with an experimental virtio patch by Julio.
That patch itself isn't ready yet though, so not included.
Other drivers compiled only.
2019 Dec 10
4
[PATCH net-next v12 0/3] netdev: ndo_tx_timeout cleanup
Yet another forward declaration I missed. Hopfully the last one ...
A bunch of drivers want to know which tx queue triggered a timeout,
and virtio wants to do the same.
We actually have the info to hand, let's just pass it on to drivers.
Note: tested with an experimental virtio patch by Julio.
That patch itself isn't ready yet though, so not included.
Other drivers compiled only.