lkml.org 
[lkml]   [2008]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Subjecte1000e fails after several S3 resumes (2.6.26 Debian, TP T60)
Date
From
Once in a while after resuming from S3 sleep, the Ethernet driver
gets confused, whereupon dhcp'ing for an IP address fails, e.g.

/* doing the dhcp: */
Listening on LPF/eth0/00:16:41:52:50:de
Sending on LPF/eth0/00:16:41:52:50:de
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
/* and so on with various intervals */

I workaround it with

modprobe -rv e1000e ; modprobe -v e1000e
(the '-v' options to make sure the module does vanish and return)

and then try again to get an address, which works. A similar failure
mode happens with the iwl3945 driver (and a similar workaround usually
succeeds).

How can I debug this issue the next time that it happens (it's about
once every two weeks)? Using 'ethtool' or 'lspci -vvvv'?

$ uname -a
Linux approx 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux

It's Debian unstable's kernel 2.6.26 based on 2.6.26.4. The laptop is a
Thinkpad T60 whose network controllers are given by lspci as

02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

Could it be caused by the kernel (and modules) getting upgraded
underneath a running system? In which case I'll just 'not do that
again' as the simplest fix, and reboot after a kernel upgrade. My
installed kernel is based on 2.6.26.6, but the running kernel is based
on 2.6.26.4 [where based on means 'with Debian's patches'].

Please CC me on any responses.

-Sanjoy

`Until lions have their historians, tales of the hunt shall always
glorify the hunters.' --African Proverb


\
 
 \ /
  Last update: 2008-10-22 15:31    [W:0.060 / U:1.432 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site