Re: Resume Issue with em(4) ALPHA7
On 9/30/18 10:12 AM, Pete Wright wrote: On 9/30/18 1:27 AM, Johannes Lundberg wrote: On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. thanks for the workaround suggestion Ali and Johannes! if there isn't a PR for this yet i'll file one now. file this PR for those playing along at home: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828 -p -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Resume Issue with em(4) ALPHA7
On 9/30/18 1:27 AM, Johannes Lundberg wrote: On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. thanks for the workaround suggestion Ali and Johannes! if there isn't a PR for this yet i'll file one now. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Resume Issue with em(4) ALPHA7
On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: > I'm having also the same problem on my Thinkpad x230. However I'm running a > minimal kernel, so usually I do kldunload/kldload if_em, > to reset the hardware and to avoid a reboot. > > Hopefully this gets fixed soon. > > Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. /Johannes Cheers, > Ali > > On Sat, Sep 29, 2018 at 7:06 PM Pete Wright wrote: > > > Hello, > > > > More suspend/resume testing on my end. This system is a desktop, so not > > critical for my daily workflow but wanted to flag it regardless. The > > system is a Lenovo m900 with skylake and em(4) NIC. Entering suspend > > works without issues, resuming seems to mostly work as well. I.e. no > > issues with display or input from keyboard or mouse. > > > > The one issue I am running into is my NIC is non-functional after > > resume. restarting the network stack via "service netif restart" does > > not work - as in no DHCP lease is aquired and no link is detected. Nor > > does manually down'ing and up'ing the interface work. I see these > > messages in my dmesg buffer after resume: > > > > in6_purgeaddr: err=65, destination address delete failed > > lo0: link state changed to DOWN > > lo0: link state changed to UP > > Link state changed to down > > em0: link state changed to DOWN > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > > > Another thing I noticed is that after resume "ifconfig" hangs for a > > couple seconds printing after printing the first line of my em0 device > > (after the flags). Not sure if that's helpful but thought it could be a > > useful datapoint. > > > > It is easy to reproduce this, so I am happy to do any additional > > debugging or testing on this. > > > > > > Cheers, > > > > -pete > > > > -- > > Pete Wright > > p...@nomadlogic.org > > @nomadlogicLA > > > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Resume Issue with em(4) ALPHA7
I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Cheers, Ali On Sat, Sep 29, 2018 at 7:06 PM Pete Wright wrote: > Hello, > > More suspend/resume testing on my end. This system is a desktop, so not > critical for my daily workflow but wanted to flag it regardless. The > system is a Lenovo m900 with skylake and em(4) NIC. Entering suspend > works without issues, resuming seems to mostly work as well. I.e. no > issues with display or input from keyboard or mouse. > > The one issue I am running into is my NIC is non-functional after > resume. restarting the network stack via "service netif restart" does > not work - as in no DHCP lease is aquired and no link is detected. Nor > does manually down'ing and up'ing the interface work. I see these > messages in my dmesg buffer after resume: > > in6_purgeaddr: err=65, destination address delete failed > lo0: link state changed to DOWN > lo0: link state changed to UP > Link state changed to down > em0: link state changed to DOWN > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > > Another thing I noticed is that after resume "ifconfig" hangs for a > couple seconds printing after printing the first line of my em0 device > (after the flags). Not sure if that's helpful but thought it could be a > useful datapoint. > > It is easy to reproduce this, so I am happy to do any additional > debugging or testing on this. > > > Cheers, > > -pete > > -- > Pete Wright > p...@nomadlogic.org > @nomadlogicLA > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Resume Issue with em(4) ALPHA7
Hello, More suspend/resume testing on my end. This system is a desktop, so not critical for my daily workflow but wanted to flag it regardless. The system is a Lenovo m900 with skylake and em(4) NIC. Entering suspend works without issues, resuming seems to mostly work as well. I.e. no issues with display or input from keyboard or mouse. The one issue I am running into is my NIC is non-functional after resume. restarting the network stack via "service netif restart" does not work - as in no DHCP lease is aquired and no link is detected. Nor does manually down'ing and up'ing the interface work. I see these messages in my dmesg buffer after resume: in6_purgeaddr: err=65, destination address delete failed lo0: link state changed to DOWN lo0: link state changed to UP Link state changed to down em0: link state changed to DOWN em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 Another thing I noticed is that after resume "ifconfig" hangs for a couple seconds printing after printing the first line of my em0 device (after the flags). Not sure if that's helpful but thought it could be a useful datapoint. It is easy to reproduce this, so I am happy to do any additional debugging or testing on this. Cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
