On Wed, Aug 18, 2010 at 10:30 PM, Eric Cope <eric.cope@gmail.com> wrote:

I opened up my laptop and removed the internal wireless card, eth1. wpa_supplicant no longer pestering me. Its an Orinoco card from 2002. Its 802.11b only WEP encryption (loosely termed).

If I could get it to work with the card in it, I'd be happy, but no wireless is not an immediate show stopper.

Eric

On Wed, Aug 18, 2010 at 10:08 PM, Eric Cope <eric.cope@gmail.com> wrote:

More details. If I boot without an active network, wpa_supplicant stays dormant and the system is stable for at least 8 hours. If I boot with one active network, eth0 is my internal 10/100 card, eth1 is my wireless card that I don't want active, eth2 is a pcmcia 10/100/1000 card. If eth0 or eth2 are active, wpa_supplicant consumes ~7-8% of the cpu until events/0 erupts to 80% of the cpu. This makes no sense to me since I don't need (at least I thought) wpa_supplicant for either wired connections. How do I disable eth1 in Ubuntu 10.04? I google it, but google's responses seem to be dated for 9.x or earlier. Here are some log entries from various log files.

Here are some log entries from daemon.log. Its about 3.4MB of this
Aug 18 23:00:09 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:00:10 selenium-rc wpa_supplicant[645]: No network configuration found for the current AP
Aug 18 23:00:10 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:00:10 selenium-rc wpa_supplicant[645]: No network configuration found for the current AP
Aug 18 23:00:10 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:00:11 selenium-rc wpa_supplicant[645]: No network configuration found for the current AP

/var/log/debug has 3.9MB of this
Aug 17 18:59:21 selenium-rc kernel: [ 1813.644710] eth1: New link status: Connected (0001)
Aug 17 18:59:21 selenium-rc kernel: [ 1813.659202] eth1: New link status: Disconnected (0002)
Aug 17 18:59:22 selenium-rc kernel: [ 1814.077904] eth1: New link status: Connected (0001)
Aug 17 18:59:22 selenium-rc kernel: [ 1814.092465] eth1: New link status: Disconnected (0002)
Aug 17 18:59:22 selenium-rc kernel: [ 1814.666349] eth1: New link status: Connected (0001)

kern.log has 4.6MB of this:

Aug 18 23:01:59 selenium-rc kernel: [ 344.839603] eth1: New link status: Disconnected (0002)
Aug 18 23:02:00 selenium-rc kernel: [ 345.528158] eth1: New link status: Association Failed (0006)
Aug 18 23:02:00 selenium-rc kernel: [ 345.532784] eth1: New link status: Disconnected (0002)
Aug 18 23:02:01 selenium-rc kernel: [ 346.148602] eth1: New link status: Association Failed (0006)

syslog has 9 MB of this:

Aug 18 23:02:03 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:04 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:04 selenium-rc kernel: [ 349.234096] eth1: New link status: Association Failed (0006)
Aug 18 23:02:04 selenium-rc kernel: [ 349.234819] eth1: New link status: Disconnected (0002)
Aug 18 23:02:04 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:04 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:04 selenium-rc kernel: [ 349.863346] eth1: New link status: Association Failed (0006)
Aug 18 23:02:04 selenium-rc kernel: [ 349.868011] eth1: New link status: Disconnected (0002)
Aug 18 23:02:04 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:08 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug 18 23:02:08 selenium-rc kernel: [ 353.312185] eth1: New link status: Association Failed (0006)
Aug 18 23:02:08 selenium-rc kernel: [ 353.316797] eth1: New link status: Disconnected (0002)
Aug 18 23:02:08 selenium-rc wpa_supplicant[645]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

From the size of your files, I would say that network manager was crashing/swapping attempting to create a connection (called by other network resources or dependencies).

Too bad this guy beat you to it:

http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg2363366.html

You could have submitted a bug report! :(

But actually, this has been fixed in the Debian 0.2-5 kernel as part of 64bit integration bug. Ubuntu just needs is to sync from Debian. So it should be part of the next slew of updates.


# apt-get update && upgrade

(When they finally do get it over from Debian).  


At most it will be 2 months to appear in the newer version, but google often to see status.


I doubt that this is hardware related so don't think you will fix it with a new Wireless card (although that WEP is ____!)

Thanks,
Eric

On Wed, Aug 18, 2010 at 10:48 AM, Eric Cope <eric.cope@gmail.com> wrote:

I installed 10.04. I have two network interfaces, eth0 is my laptop's 10/100 port. eth1 is my laptop's 802.11b wireless port. This makes replacing the network cards more difficult, especially since the laptop is older and not worth finding a replacement network card. I decided to take my laptop to my day job to debug while my day job's work was simulating. I did not plug my laptop into the network, which is why I unplugged eth0 (not to try and fix eth1).

Thanks again,
Eric

On Wed, Aug 18, 2010 at 10:34 AM, Dazed_75 <lthielster@gmail.com> wrote:

I would hate to see you back out two years worth of advances in ubuntu. I don't think that you ever said which version you just installed, but assuming it was 10.04 or even a 10.10 alpha release, I might be tempted to try 9.10 which was a very good release. On another note, 10.04.1 was released which is the pre-planned patch release for the 10.04 LTS (Long Term Support) and it fixes some things so you could even try that although if you have 10.04 installed you only need to get the updates to be on 10.04.1.

Hmmm, just noticed that you said unplugging eth0 (ZERO, not ONE) fixes the problem. Does that mean you have two network cards? Perhaps you are seeing a conflict of some sort. Why did you choose to unplug eth0 instead of eth1 which you were getting the messages for?

On Wed, Aug 18, 2010 at 8:48 AM, Eric Cope <eric.cope@gmail.com> wrote:
When I unplugged the network cable, eth0, dmesg stays clean.
I'll investigate more later today. As a historical note, I ran Ubuntu 8.10 (I think) for months on this machine. Perhaps I should roll my install back.

Eric

On Wed, Aug 18, 2010 at 8:34 AM, Stephen <cryptworks@gmail.com> wrote:
All the weird networking i have run into in Ubuntu has been because of
Network manager. It tends to fight with any "conventional"
configuration of the network.

http://en.wikipedia.org/wiki/NetworkManager

On Wed, Aug 18, 2010 at 8:30 AM, Dazed_75 <lthielster@gmail.com> wrote:
> Doing a Google search on "eth1: New link status: Connected (0001)" yields
> about 58,000 results. I looked through a few but did not find a solution.
>
> I did find one user who said it was frustrating because he did not have the
> problem with the previous version of ubuntu (he did not say which one).
> Since yours was a new installation, you might want to try an older ubuntu
> first just to try eliminating hardware as the cause. Let me know if you
> need a CD for that.
>
> On Wed, Aug 18, 2010 at 6:56 AM, Stephen <cryptworks@gmail.com> wrote:
>>
>> This looks like network manager is on play check itsconfig or turn it off
>>
>> On Aug 17, 2010 11:17 PM, "Eric Cope" <eric.cope@gmail.com> wrote:
>>
>> I looked in dmesg... I get :
>>
>> [4951.040817] eth1: New link status: Connected (0001)
>> [4952.436157] eth1: New link status: Connected (0001)
>>
>> I tried "sudo ifdown eth1" ... I get interface eth1 not configured.
>>
>> Any ideas?
>>
>> Thanks,
>> Eric
>>
>> On Tue, Aug 17, 2010 at 11:11 PM, Eric Cope <eric.cope@gmail.com> wrote:
>> >
>> > I tried both acpi=off...
>>
>> ---------------------------------------------------
>
> --
> Dazed_75 a.k.a. Larry
>
> The spirit of resistance to government is so valuable on certain occasions,
> that I wish it always to be kept alive.
> - Thomas Jefferson

--

A mouse trap, placed on top of your alarm clock, will prevent you from
rolling over and going back to sleep after you hit the snooze button.

http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss