2001-02-12 16:10:34

by Gordon Sadler

[permalink] [raw]
Subject: 2.2.19ac-pre9 lo interface Broke

Not sure how else to put it...

$ sudo ifup lo
SIOCSIFADDR: Bad file descriptor
lo: unknown interface: Bad file descriptor
lo: unknown interface: Bad file descriptor

$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:A0:C9:D9:21:B9
inet addr:24.142.168.193 Bcast:255.255.255.255 Mask:255.255.254.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:8223 errors:0 dropped:0 overruns:0 frame:0
TX packets:7373 errors:0 dropped:0 overruns:0 carrier:0
collisions:3 txqueuelen:100
RX bytes:8241275 (7.8 Mb) TX bytes:2271020 (2.1 Mb)
Interrupt:15 Base address:0x1000

Works just fine same box, same config with 2.2.18ac-pre24.

Debian tools: ifupdown 0.6.4-3 (ifup ifdown)
net-tools 1.58-1 (ifconfig)

Intel Etherexpress 10/100 eepro100
CONFIG_EEXPRESS_PRO100=y

Any ideas?

Please CC any replies.

Gordon Sadler


2001-02-13 20:30:09

by Gordon Sadler

[permalink] [raw]
Subject: Re: 2.2.19ac-pre9 lo interface Broke

I have some further info here.
I performed strace on ifup -a and ifdown -a.

They aren't more than 4Kb each, but I'll cut and paste what appear to be
most relevant:

ifup.strace:
fork() = 17974
wait4(17974, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 17974
--- SIGCHLD (Child exited) ---
fork() = 17976
wait4(17976, SIOCSIFADDR: Bad file descriptor
lo: unknown interface: Bad file descriptor
lo: unknown interface: Bad file descriptor
[WIFEXITED(s) && WEXITSTATUS(s) == 255], 0, NULL) = 17976
--- SIGCHLD (Child exited) ---

ifdown.strace:
munmap(0x40018000, 4096) = 0
fork() = 17989
wait4(17989, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 17989
--- SIGCHLD (Child exited) ---
fork() = 17991
wait4(17991, lo: unknown interface: Bad file descriptor
[WIFEXITED(s) && WEXITSTATUS(s) == 255], 0, NULL) = 17991
--- SIGCHLD (Child exited) ---

I think a better question would be, does anyone here have any ideas
where I might look to correcting this? Since it did not occur with same
tools under 2.2.18pre24, should I assume the kernel is at fault and look
there? Or maybe the eepro module code? I notice quite a bit of
discussion concerning this driver, but all (?) relating to 2.4.x

Can anyone point a finger?

Thanks
Gordon Sadler

2001-02-13 20:34:19

by Alan

[permalink] [raw]
Subject: Re: 2.2.19ac-pre9 lo interface Broke

> I have some further info here.
> I performed strace on ifup -a and ifdown -a.

Unfortunately you traced the script execution and nothing more useful so
I cant tell.

2001-02-13 21:07:26

by Scott Ashcroft

[permalink] [raw]
Subject: Re: 2.2.19ac-pre9 lo interface Broke

Gordon Sadler wrote:
>
> I have some further info here.
> I performed strace on ifup -a and ifdown -a.
>
> They aren't more than 4Kb each, but I'll cut and paste what appear to be
> most relevant:
>
> ifup.strace:
> fork() = 17974
> wait4(17974, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 17974
> --- SIGCHLD (Child exited) ---
> fork() = 17976
> wait4(17976, SIOCSIFADDR: Bad file descriptor
> lo: unknown interface: Bad file descriptor
> lo: unknown interface: Bad file descriptor
> [WIFEXITED(s) && WEXITSTATUS(s) == 255], 0, NULL) = 17976
> --- SIGCHLD (Child exited) ---
[snip]
>
> Can anyone point a finger?

Debian bug #85774
http://cgi.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=85774

ifconfig broke, nothing to do with the kernel.

Cheers,
Scott

2001-02-13 22:01:49

by Gordon Sadler

[permalink] [raw]
Subject: Re: 2.2.19ac-pre9 lo interface Broke

Sorry for all the fuss, I've been reliably informed, I put my foot in my
own mouth...

It was my net-tools package from Debian -(. I missed the fact I upgraded
some packages same day I upgraded my kernel.

I'll drop off the list again now. Sorry for the bother.