Opened 11 years ago
Closed 6 years ago
#10919 closed bug (fixed)
ifconfig del KDLs reproducibly
Reported by: | jackburton | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Network & Internet/Stack | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #10930, #12561 | |
Platform: | All |
Description
Doing an "ifconfig del /dev/net/<anydriver>/<anyinterface> KDLs horribly. I didn't post the KDL output because it's reproducible everytime. Will do if requested, though.
Attachments (3)
Change History (23)
comment:1 by , 11 years ago
comment:4 by , 11 years ago
comment:5 by , 11 years ago
comment:6 by , 11 years ago
More information: I cannot reproduce it within VirtualBox. It's 100% reproducible on my laptop.
comment:8 by , 10 years ago
Diver, could you try again ? Since I update my Haiku install lately, I cannot reproduce it anymore on real hardware, either.
comment:9 by , 10 years ago
Hrev48254 gcc4 Running this command causes KDL: ifconfig del /dev/net/ipro1000/0 ; ifconfig /dev/net/ipro1000/0 up This is on real hardware. I'll attach a listdev and photo of KDL shortly. Would a serial debug log be useful?
by , 10 years ago
Attachment: | listdev_dc7900 added |
---|
by , 10 years ago
Attachment: | IMG_0185.JPG added |
---|
comment:10 by , 9 years ago
I still can't reproduce this, on a current revision, on VirtualBox. I can't test on real hardware anymore, though. Can you still reproduce it, diver ?
comment:11 by , 9 years ago
I can still reproduce it in hrev49530 with VirtualBox 4.1.28 with NAT mode by running a few pings while deleting an interface.
comment:13 by , 9 years ago
Nope, still can't reproduce. It's either timing dependent, or... don't know.
comment:14 by , 9 years ago
Try to start pinging or create some network activity in some other way and also
while : ; do ifconfig del /dev/net/ipro1000/0 ; ifconfig /dev/net/ipro1000/0 up ; done
comment:15 by , 7 years ago
Blocking: | 10930 added |
---|
comment:16 by , 7 years ago
Blocking: | 12561 added |
---|
comment:18 by , 6 years ago
I added a tentative fix in gerrit. Change 469. With "tentative" I just mean it needs to be reviewed to be sure it doesn't cause other problems. But it definitely fixes this problem.
comment:19 by , 6 years ago
Axel, could you review the change ? Since you are one of the main contributors of this part of the code, I guess you can tell if it's okay or not.
That doesn't seem like a good reason to omit the output. That makes the assumption that it isn't something about your configuration that makes it reliably reproducible, and further, if nothing else, it would be nice to save the person who winds up looking into it the time of having to reproduce it just to find out where to start looking.