What I think is happening is that after it come out of suspend the device memory mapping is either no longer mapped or it's somehow changed. The reason I say this is:
[ 1569.219047] e1000e 0000:00:19.0: eth0: Error reading PHY register [ 1569.437327] mount.crypt[8294]: segfault at 0 ip 00007fa19feb9a0e sp 00007fffde4e7bd0 error 4 in mount.crypt[7fa19feb2000+a000] [ 1570.014032] e1000e 0000:00:19.0: eth0: Error reading PHY register [ 1570.809335] e1000e 0000:00:19.0: eth0: Error reading PHY register There should be no errors from the driver when reading the PHY. This is also probably why ethtool does not work after the suspend. BTW, does ethtool work before the first time the systems been suspended? Please try this if you haven't. Anyway, I think suspend or resume is doing something bad to the system. Can you please try something like the latest 3.0 stable kernel and see if it's working there? This is most likely not a driver issue but I guess it still could be. Please let me know if the 3.0 kernel works. Thanks, John ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
