baselayout-1.11.2 -- net daemon-scripts cause hard crash when running net-startup scripts (/etc/init.d/net.eth1) with a loaded system i have had 3 or 4 crashes with net script in baselayout-1.11.2 after running them on and off, intermintiatly 2 or 3 times on various interfaces. in two of these occations tne net config file was nullified (this could have been because they were open at the time and it may have caused the crashes as well, i was using kedit and i dont how tightly it holds those files). every time it caused substantial file corruption in the nodes (using 5 xfs partions on 2 sata drives) which was repairable but caused latent anomalies (konqueror not loading but not really saying much either, kde sort of fading away like it was on drugs). given the nature of the crash id say it was in kernel space since the system crashed and rebooted imediately into the script. i suspect that the crashes have something to do with all of the modules being loaded at once or with at one or more of the modules causing the kernel greif. ive tryed to prevent them all from loading but wind up srcewing up the script. when the net file is erased dhcpd starts but i dont have a dhcpd server, dhcpd daemon doesnt time out, it would be nice if it did. previously it didnt work at all or i couldnt get it to work, which made it hard to configure new routers. im also able to start two interfaces on gateways, now that the route funcion excepts the whole bussiness end of the command line. i was also able to get at an eql interface to run, im not sure if i need to enslave anything or not though. i think if there was a way to control the various network functions in the net conf file it would be better than loading all of the modules at once even if they arent doing anything just for sake of less clutter. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.
kernel bug, has nothing to do with baselayout
i think ive isolated it to coldplug. the only reason i can see that might cause it to do that is if it found other cards modules since i have many modules which i dont ordiarily run which is why i made them modules i can see the benifit of having this run on in the script but only in certian situations. on pcmcia systems it would do great, and theres a whole algorithm for these situations that would go along. the situation im in isn't one where i would want modules to be loaded but theres benifit to having a dynamic interface handler or at least in this case not having one. just having the ability to choose one of a few of these generalized paths would at let me bring all systems up without much of a hassle.
Jacob, btw the "modules" that are loaded by baselayout-1.11.2 for network configuration aren't kernel modules. They're script modules. See /lib/rcscripts/net.modules.d
i had some notion of this but i really dont know how it works to be honest. the only thing i can really say, and take it for what its worth, is that when i ran "/etc/init.d/net.eth0 restart" the system was prone to crashing. when i run coldplug the same thing happens only in this case my /etc/conf.d/net isnt full of "@^@^@^^@^@^@^@^@...". when it is erased, the system hangs at start-up because it cant get an address. whether or not this constitutes a bug and whats to be done about it, i really dont know. i realize that this port is masked and i take on certain risks installing it. i thought however that the results of doing so might be of some use in development.
