FS#18018 - [dhcpcd] breaks kernel

Attached to Project: Arch Linux
Opened by Jax Prax (poisonkiller) - Tuesday, 26 January 2010, 16:17 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 26 January 2010, 22:00 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Ronald van Haren (pressh)
Isenmann Daniel (ise)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When the latest version of dhcpcd is installed (dhcpcd-5.1.4-2) and computer is rebooted, bootup hangs at Network for a while and then fails.

Additional info:
* package version(s) : 5.1.4-2
* config and/or log files etc.


Steps to reproduce:
Install dhcpcd-5.1.4-2?
This task depends upon

Closed by  Ronald van Haren (pressh)
Tuesday, 26 January 2010, 22:00 GMT
Reason for closing:  Duplicate
Comment by Thomas Dziedzic (tomd123) - Tuesday, 26 January 2010, 17:11 GMT
How does it break the kernel? If it fails, that only means it failed to get an ip. Need more info.
Comment by Frederic Bezies (fredbezies) - Tuesday, 26 January 2010, 17:15 GMT
Seeing the same problem. I have to use an ubuntu livecd to grab package to downgrade ip.

dhpcd cannot give anymore an ip. I was thinking wicd to be guilty. Will post some infos as soon as I get a working connexion back.
Comment by Frederic Bezies (fredbezies) - Tuesday, 26 January 2010, 17:26 GMT
dhcpcd package is guilty. I downgraded from dhcpcd-5.1.4-1 to dhcpcd-5.1.3-1 and it works again !

Comment by Jax Prax (poisonkiller) - Tuesday, 26 January 2010, 17:43 GMT
I'm sorry, tom, I am just enough computer savvy to make this bug report, but no more (it means that I can't give you more info)...
I only made this bug report to warn people about breaking their connection to the internet.
Comment by Ivan Bulatovic (combuster) - Tuesday, 26 January 2010, 18:50 GMT
It fails to get an ip, I'm connecting with netcfg and have testing enabled. With 5.1.4-1 it connects just fine, with 5.1.4-2 it wont.

dmesg output:

87.253327] Registered led device: iwl-phy0::radio
[ 87.253352] Registered led device: iwl-phy0::assoc
[ 87.253623] Registered led device: iwl-phy0::RX
[ 87.253648] Registered led device: iwl-phy0::TX
[ 89.385096] wlan0: deauthenticating from 00:15:77:41:38:5e by local choice (reason=3)
[ 89.385368] wlan0: direct probe to AP 00:15:77:41:38:5e (try 1)
[ 89.388534] wlan0: direct probe responded
[ 89.388543] wlan0: authenticate with AP 00:15:77:41:38:5e (try 1)
[ 89.390881] wlan0: authenticated
[ 89.390927] wlan0: associate with AP 00:15:77:41:38:5e (try 1)
[ 89.393476] wlan0: RX AssocResp from 00:15:77:41:38:5e (capab=0x401 status=0 aid=1)
[ 89.393484] wlan0: associated
[ 102.399104] wlan0: deauthenticating from 00:15:77:41:38:5e by local choice (reason=3)
[ 102.399176] wlan0: deauthenticating from 00:15:77:41:38:5e by local choice (reason=3)
Comment by Assaf Sapir (meijin) - Tuesday, 26 January 2010, 21:46 GMT
in my case, its give me:

dhcpcd: wlan0: offered 192.168.2.104 from 192.168.2.1
dhcpcd: wlan0: NAK: from 192.168.2.1

few times, and then timeout.
i tried manualy, and with networkmanager - same results

Loading...