On Thu, Apr 19, 2001 at 01:32:48PM -0700, Michael Durket wrote: > I've installed the latest beta release and it's exacerbating > a problem I've seen only occasionally with the former RedHat > beta, namely: > > 1) the ifup of ctc0 fails intermittently > > 2) the startup scripts incorrectly report that it succeeded > > > Here's an excerpt from the log of what happens: > > Apr 19 09:29:50 linux3-ibm network: Setting network parameters: succeeded > Apr 19 09:29:50 linux3-ibm network: Bringing up interface lo: succeeded > Apr 19 09:29:51 linux3-ibm ifup: SIOCSIFFLAGS: Cannot allocate memory > Apr 19 09:29:51 linux3-ibm ifup: SIOCADDRT: Network is unreachable > Apr 19 09:29:51 linux3-ibm ifup: SIOCADDRT: Network is unreachable > Apr 19 09:29:51 linux3-ibm network: Bringing up interface ctc0: succeeded > > > As I said, this problem occurred rarely on the previous beta. I can generally > reproduce it on the new beta by abruptly doing a re-ipl of linux (not via > a shutdown but rather #cp ipl 200 while it's running). The reload will > not bring up the network properly, but a subsequent shutdown -h followed > by an ipl 200 will. > > (Note: this is not my normal mode of reloading - I'm playing around with something > that keeps hanging my system, necessitating the forcible restart). > > Also note that the SIOCSIFFLAGS message is originating from a general flag-setting > subroutine in ifconfig - too bad the author(s) of ifconfig didn't see fit to > also log the flag they were being asked to set. If I interpret the error message correctly, your kernel has problems allocating memory to get this kernel syscall done. The question for me is: Is this not happening if you use a stock gcc 2.95.2 compiler instead of the 2.95.3 we have used as a compiler? Or are other things in your setup screwed at the moment? Thanks, Florian La Roche
