Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1611700 > unrolled thread
| Started by | Jisheng Zhang <jszhang@marvell.com> |
|---|---|
| First post | 2017-03-29 11:00 +0200 |
| Last post | 2017-03-29 23:20 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running Jisheng Zhang <jszhang@marvell.com> - 2017-03-29 11:00 +0200
Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running Andrew Lunn <andrew@lunn.ch> - 2017-03-29 15:00 +0200
Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running David Miller <davem@davemloft.net> - 2017-03-29 23:20 +0200
| From | Jisheng Zhang <jszhang@marvell.com> |
|---|---|
| Date | 2017-03-29 11:00 +0200 |
| Subject | [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running |
| Message-ID | <tqhCp-4pL-7@gated-at.bofh.it> |
I found a bug by:
0. boot and start dhcp client
1. echo mem > /sys/power/state
2. resume back immediately
3. don't touch dhcp client to renew the lease
4. ping the gateway. No acks
Usually, after step2, the DHCP lease isn't expired, so in theory we
should resume all back. But in fact, it doesn't. It turns out
the rx mode isn't resumed correctly. This patch fixes it by adding
mvneta_set_rx_mode(dev) in the resume hook if interface is running.
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
Since v1:
- rebased to the latest net-next tree and explictly mention it
drivers/net/ethernet/marvell/mvneta.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/mvneta.c b/drivers/net/ethernet/marvell/mvneta.c
index aebbc5399a06..cc126204dc4d 100644
--- a/drivers/net/ethernet/marvell/mvneta.c
+++ b/drivers/net/ethernet/marvell/mvneta.c
@@ -4449,8 +4449,11 @@ static int mvneta_resume(struct device *device)
mvneta_fixed_link_update(pp, dev->phydev);
netif_device_attach(dev);
- if (netif_running(dev))
+ if (netif_running(dev)) {
mvneta_open(dev);
+ mvneta_set_rx_mode(dev);
+ }
+
return 0;
}
#endif
--
2.11.0
[toc] | [next] | [standalone]
| From | Andrew Lunn <andrew@lunn.ch> |
|---|---|
| Date | 2017-03-29 15:00 +0200 |
| Subject | Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running |
| Message-ID | <tqlmG-6Yd-33@gated-at.bofh.it> |
| In reply to | #1611700 |
On Wed, Mar 29, 2017 at 04:47:19PM +0800, Jisheng Zhang wrote:
> I found a bug by:
>
> 0. boot and start dhcp client
> 1. echo mem > /sys/power/state
> 2. resume back immediately
> 3. don't touch dhcp client to renew the lease
> 4. ping the gateway. No acks
>
> Usually, after step2, the DHCP lease isn't expired, so in theory we
> should resume all back. But in fact, it doesn't. It turns out
> the rx mode isn't resumed correctly. This patch fixes it by adding
> mvneta_set_rx_mode(dev) in the resume hook if interface is running.
>
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
[toc] | [prev] | [next] | [standalone]
| From | David Miller <davem@davemloft.net> |
|---|---|
| Date | 2017-03-29 23:20 +0200 |
| Subject | Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running |
| Message-ID | <tqtaA-4hp-55@gated-at.bofh.it> |
| In reply to | #1611700 |
From: Jisheng Zhang <jszhang@marvell.com> Date: Wed, 29 Mar 2017 16:47:19 +0800 > I found a bug by: > > 0. boot and start dhcp client > 1. echo mem > /sys/power/state > 2. resume back immediately > 3. don't touch dhcp client to renew the lease > 4. ping the gateway. No acks > > Usually, after step2, the DHCP lease isn't expired, so in theory we > should resume all back. But in fact, it doesn't. It turns out > the rx mode isn't resumed correctly. This patch fixes it by adding > mvneta_set_rx_mode(dev) in the resume hook if interface is running. > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com> > --- > Since v1: > - rebased to the latest net-next tree and explictly mention it Applied.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web