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
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
|
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
Tuesday, 26 January 2010, 22:00 GMT
Reason for closing: Duplicate
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.
I only made this bug report to warn people about breaking their connection to the internet.
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)
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