Bug 106171
| Summary: | Regression causes "ip" command to crash, leaving the user without any networking | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Yill Din (justincase) |
| Component: | IPV4 | Assignee: | Stephen Hemminger (stephen) |
| Status: | NEW --- | ||
| Severity: | high | CC: | dev, shemming, szg00000 |
| Priority: | P1 | ||
| Hardware: | ARM | ||
| OS: | Linux | ||
| Kernel Version: | 4.2.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Process ip (pid: 252, stack limit = 0xed7a4220) Stack: (0xed7a5a58 to 0xed7a6000)
dmesg |
||
Tested on Udoo Dual using Arch ARM. This is a bug in the freescale network driver. Not ip command or the stack. Could you please attach the full dmesg log and the ip command line, so I can see what is going on here. Thanks. Created attachment 190591 [details] dmesg I believe it is sending the following command on boot: ip link set "wlan0" up When running the command manually it causes the tty/serial shell to crash. Full dmesg of bootup attached. Here is the netctl source code which shows the ip link commands it uses https://projects.archlinux.org/netctl.git/tree/src/lib/network This issue should already be fixed in 4.3-rc. I've requested the relevant patches to be added into 4.2 stable. |
Created attachment 190481 [details] Process ip (pid: 252, stack limit = 0xed7a4220) Stack: (0xed7a5a58 to 0xed7a6000) Between kernel version 4.1.7 and 4.2.0 something caused networking to be left non-functioning. I can confirm the bug is still in mainline 4.2.3. Attached is the stack trace showing up during boot of the device with 4.2.3 kernel. I have since regressed to 4.1.x and networking works fine again. I had one other user confirm this bug via Freenode IRC.