O.K., so amazingly this is solved, at least on the practical end. I have no idea why this works, and I've provided some more information below if people want to pursue this or for others trying to solve this problem, but the solution that worked for me was powering off the computer, unplugging it, removing the battery, waiting 30 seconds, plugging it back in, reattaching the battery, and powering back up. I've been monitoring htop and CPU usage is normal with eth0 up. No idea if eth0 works as I can't currently test it, but I have no reason to believe that it doesn't.
Wireless is still wonky, but that's another issue, even if it's possibly related. This solution was found from here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/53739 Thanks for all the help! More information is below for anyone who wants it. Kyle vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv On Mon, Mar 7, 2011 at 7:24 PM, Slicky Johnson <slickyjohn...@gmail.com> wrote: > I have the identical hardware and also use wicd. I've not experienced > any of the above. I've commented out eth0 from /etc/network/interfaces > as I don't even own a cable. > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > > #allow-hotplug eth0 > #iface eth0 inet dhcp Huh. This is identical to my /etc/network/interfaces file, actually. > It's been that way since Lenny. Have you looked around > http://www.thinkwiki.org/wiki/ThinkWiki for possible problems? This > would be the first I've heard of it and any time something with a T61 > comes up I pay pretty close attention. That's a good idea, I hadn't checked there. Unfortunately, I don't see anything there, either by searching around, by checking the Category:T61 page (http://www.thinkwiki.org/wiki/Category:T61), the page for my wireless card (which if I remember correctly is http://www.thinkwiki.org/wiki/Intel_PRO/Wireless_3945ABG_Mini-PCI_Express_Adapter), or the page for what they say is my ethernet card (http://www.thinkwiki.org/wiki/Intel_Gigabit_Ethernet_(10/100/1000)_PCI-Express). However, you're right that it may be a Thinkpad issue - the people on the forum I quoted earlier had a Thinkpad X61, which has the same wireless and ethernet cards. However, after searching around, there's other reports of similar behavior going back a while, such as here, http://lkml.indiana.edu/hypermail/linux/kernel/0605.2/0212.html, although I couldn't get much out of that. On Mon, Mar 7, 2011 at 7:29 PM, Ron Johnson <ron.l.john...@cox.net> wrote: > Anything in syslog? Well, if I bring up eth0 ("# ifconfig eth0 up"), wait for it to lag, and then turn eth0 off again ("# ifconfig eth0 down"), this is what shows up in syslog: Mar 7 23:08:03 mjollnir kernel: [26127.412486] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X Mar 7 23:08:03 mjollnir kernel: [26127.468269] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X Mar 7 23:08:03 mjollnir kernel: [26127.468919] ADDRCONF(NETDEV_UP): eth0: link is not ready The only entry in /var/log/messages is fairly innocuous (I think): Mar 7 23:08:03 mjollnir kernel: [26127.468919] ADDRCONF(NETDEV_UP): eth0: link is not ready And it also shows up in dmesg (via "dmesg | tail"): [26127.412486] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X [26127.468269] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X [26127.468919] ADDRCONF(NETDEV_UP): eth0: link is not ready I just Googled around for some of that stuff, but I'm way out of my league and don't really know what that means or if it's normal or not. Does that mean anything to you? Now that things are working again, those entries do not show up after using ifconfig to raise and lower the eth0 interface. Kyle -- Kyle Barbour k...@kylebarbour.org (415) 238-9953 San Francisco, CA, USA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinx6nh60pgosr_7cqqey2mpvi_zzsm2h9rur...@mail.gmail.com
