Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31135 - [dhcpcd,networkmanager] segfaults when connecting to Wifi

Attached to Project: Arch Linux
Opened by Franz Nemeth (franzor) - Wednesday, 15 August 2012, 11:50 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 06 September 2012, 19:23 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Ionut Biru (wonder)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Today my dhcpcd segfaulted during establishing connection with my home wifi.
Since the first segfault, it kept segfaulting everytime I tried to connect to any wireless network.
dhcpcd works fine when connecting to wired networks.
I am using networkmanager but I tested whether I get the same error using wicd and I do.


Additional info:
* package version(s): dhcpcd 5.6.0-1
* this is from the everything.log:
localhost dhcpcd[13134]: version 5.6.0 starting
localhost dhcpcd[13134]: wlan0: sending IPv6 Router Solicitation
localhost dhcpcd[13134]: wlan0: rebinding lease of 192.168.1.3
localhost NetworkManager[424]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
localhost dhcpcd[13134]: wlan0: Router Advertisement from fe80::a221:b7ff:feab:9a88
localhost NetworkManager[424]: <info> (wlan0): DHCPv4 state changed preinit -> (null)
localhost dhcpcd[13134]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
localhost dhcpcd[13134]: wlan0: checking for 192.168.1.3
localhost NetworkManager[424]: <info> (wlan0): DHCPv4 client pid 13134 exited with status -1
localhost NetworkManager[424]: <warn> DHCP client died abnormally
localhost NetworkManager[424]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
localhost NetworkManager[424]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
localhost NetworkManager[424]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
localhost kernel: [13626.076533] dhcpcd[13134]: segfault at 0 ip 00000000004122c0 sp 00007fff7bab9ec0 error 6 in dhcpcd[400000+1c0


Steps to reproduce:
* Connect with any wireless Network.
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 06 September 2012, 19:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.6.2 in [testing]

Thanks Roy.
Comment by Fazlul Shahriar (fhs) - Thursday, 16 August 2012, 03:00 GMT
I have the same issue, but with wired connection (wireless
works fine). I can't reproduce the crash outside of
networkmanager. A workaround for now is to install dhclient
package and restart networkmanager.

NetworkManager[26077]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
dhcpcd[26372]: version 5.6.0 starting
dhcpcd[26372]: eth0: sending IPv6 Router Solicitation
dhcpcd[26372]: eth0: rebinding lease of 192.168.2.2
dhcpcd[26372]: eth0: Router Advertisement from fe80::21c:dfff:fe38:b7f1
dhcpcd[26372]: eth0: adding address 2002:43f3:2fa0:1234:21e:37ff:fe86:3d87
dhcpcd[26372]: eth0: vltime 300 seconds, pltime 120 seconds
dhcpcd[26372]: eth0: acknowledged 192.168.2.2 from 192.168.2.1
dhcpcd[26372]: eth0: checking for 192.168.2.2
NetworkManager[26077]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
NetworkManager[26077]: <info> Activation (eth0) successful, device activated.
NetworkManager[26077]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
NetworkManager[26077]: <info> (eth0): DHCPv4 state changed nbi -> preinit
NetworkManager[26077]: <info> (eth0): DHCPv4 state changed preinit -> (null)
avahi-daemon[683]: Registering new address record for 2002:43f3:2fa0:1234:21e:37ff:fe86:3d87 on eth0.*.
avahi-daemon[683]: Withdrawing address record for fe80::21e:37ff:fe86:3d87 on eth0.
kernel: [45773.277812] dhcpcd[26372]: segfault at 0 ip 00000000004122c0 sp 00007fffd5d30900 error 6 in dhcpcd[400000+1c000]
NetworkManager[26077]: <info> (eth0): DHCPv4 client pid 26372 exited with status -1
NetworkManager[26077]: <warn> DHCP client died abnormally
Comment by Fazlul Shahriar (fhs) - Thursday, 16 August 2012, 03:14 GMT
I see what's going on now. If you set the IPv6 Settings
Method to "Ignore" (which I had for my wireless profile),
you don't get the crash. If you set it to "Link-Local Only"
(which I had for my wired profile), you get the crash.
Comment by Jelle van der Waa (jelly) - Thursday, 16 August 2012, 19:41 GMT
Please provide debubing straces and try to get in contact with upstream.
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Comment by Franz Nemeth (franzor) - Friday, 17 August 2012, 02:36 GMT
I can confirm the IPv6 thing. It also crashes when you set it to "Automatic" or "Automatic, DHCP Only"
Comment by Fazlul Shahriar (fhs) - Friday, 17 August 2012, 06:08 GMT
I can't seem to submit a bug report upstream. Their Trac
website thinks I'm spamming and I don't see any way to
register.

Here is the stack trace:

Core was generated by `/sbin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action eth0'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000411a94 in ipv6ns_sendprobe (arg=0x17db920) at ipv6ns.c:187
187 sndhdr.msg_iov[0].iov_base = rap->ns;
(gdb) bt
#0 0x0000000000411a94 in ipv6ns_sendprobe (arg=0x17db920) at ipv6ns.c:187
#1 0x000000000040a350 in start_eloop () at eloop.c:302
#2 0x0000000000409ce8 in main (argc=<optimized out>, argv=<optimized out>)
at dhcpcd.c:2110
Comment by Roy Marples (rsmarples) - Monday, 03 September 2012, 15:13 GMT
This should be fixed in dhcpcd-5.6.2 which as released earlier today.
Hopefully someone can package it for arch soon!

Loading...