Most recent kernel where this bug did not occur:2.6.13 Distribution: Fedora Core 4 Hardware Environment: IBM T40 laptop Software Environment: Fedora Core 4 + 2.6.14-rc3 Problem Description: NetworkManager appears to crash on startup with 2.6.14-rc kernels. Steps to reproduce: Running: /usr/bin/NetworkManager --no-daemon Produces: ... NetworkManager: <information> Now managing wired device 'eth0'. h*** glibc detected *** /usr/bin/NetworkManager: corrupted double-linked list: 0x08088c60 *** ======= Backtrace: ========= /lib/libc.so.6[0x43378248] /lib/libc.so.6(__libc_free+0x77)[0x4337865f] /lib/libiw.so.28(iw_process_scan+0x245)[0x438eabcf] /lib/libiw.so.28(iw_scan+0x51)[0x438eade8] /usr/bin/NetworkManager[0x805a096] /usr/bin/NetworkManager[0x805ca14] /usr/bin/NetworkManager[0x805dca5] /lib/libc.so.6(__libc_start_main+0xdf)[0x43329d5f] /usr/bin/NetworkManager[0x804cb11] ... Full output will be attached shortly.
Created attachment 6222 [details] output from running NetworkManager
It's not clear that it's the kernel who is reponsible of this. Shouldnt this be reported to networkmanager developers first...?
Probably true. However since something in the kernel (If I go back to 2.6.13 NetworkManager works fine) and triggers the issue I figured I'd file a kernel bug just in case.
As a NetworkManager and kernel developer, I can squarely place the blame: On iwlib. iwlib 28pre10 (the latest) should fix this problem.
Closing bug as not kernel. Feel free to reopen if iwlibs does not cut it.