> -----Original Message----- > From: YunQiang Su [mailto:wzss...@gmail.com] > Sent: Monday, March 04, 2013 7:58 AM > To: Ben Hutchings > Cc: e1000-de...@lists.sourceforge.net; 702...@bugs.debian.org > Subject: Re: [E1000-devel] Bug#702245: Thinkpad T410s cannot detect link > > On Mon, Mar 4, 2013 at 9:47 PM, Ben Hutchings <b...@decadent.org.uk> > wrote: > > Control: tag -1 upstream > > Control: forwarded -1 e1000-de...@lists.sourceforge.net > > > > On Mon, 2013-03-04 at 20:58 +0800, YunQiang Su wrote: > >> Package: linux > >> Version: 3.8-1~experimental.1 > >> > >> After upgrade to 3.8-1~experimental.1, my Thinkpad T410s cannot > detect > >> cable link now. > >> While it works well on 3.2, 3.5, 3.6 and 3.7 kernel. > >> > >> lspci shows > >> > >> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network > >> Connection (rev 06) > > > > I'm forwarding this to the Intel network driver developers. > > > > You will probably need to provide some additional information: > > - All boot messages relating to this device > > ('grep 00:19.0 /var/log/dmesg' should show you them) > syq@syq-t410s> sudo grep 00:19.0 /var/log/dmesg > > ~ > [ 0.739973] pci 0000:00:19.0: [8086:10ea] type 00 class 0x020000 > [ 0.740016] pci 0000:00:19.0: reg 10: [mem 0xf2500000-0xf251ffff] > [ 0.740037] pci 0000:00:19.0: reg 14: [mem 0xf2525000-0xf2525fff] > [ 0.740058] pci 0000:00:19.0: reg 18: [io 0x1820-0x183f] > [ 0.740203] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold > [ 1.547804] e1000e 0000:00:19.0: setting latency timer to 64 > [ 1.547977] e1000e 0000:00:19.0: Interrupt Throttling Rate > (ints/sec) set to dynamic conservative mode > [ 1.548068] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X > [ 1.730393] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width > x1) 5c:ff:35:04:9b:22 > [ 1.730402] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network > Connection > [ 1.730484] e1000e 0000:00:19.0 eth0: MAC: 9, PHY: 10, PBA No: A002FF-0FF > > > - Output of 'ethtool eth0' (or whatever the interface name is) > This is run when no cable plugged in. > Settings for eth0: > Cannot get device settings: No such device > Cannot get wake-on-lan settings: No such device > Cannot get message level: No such device > Cannot get link status: No such device > No data available
This may be related to some runtime power management issues for which there are a number of patches currently in test. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/804857e1f29aac47bf68c404fc60a1844d02f...@orsmsx102.amr.corp.intel.com
