Re: [SLE] "Failed" messages on boot, but the services are running?
Why is it that I see lots of 'failed' messages when I boot my SuSE Linux laptop, but the services which are reported to have failed are actually up and running just fine?
I'm running SuSE 9.0. This problem didn't happen with the 2.4 kernel, only with 2.6. I've tried Kraxel's 2.6 kernel RPM, and also a kernel I've compiled myself, and I get the same results with each. When I look at /var/log/boot.msg I see this line at the end, summing up the services which failed to start:
This problem with kernel 2.6 went away for me after I disabled kernel preemption. It is likely a race condition in startproc. Is there a patch available for it? -- Eric __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html
Eric Bloodworth wrote:
Why is it that I see lots of 'failed' messages when I boot my SuSE Linux laptop, but the services which are reported to have failed are actually up and running just fine?
I'm running SuSE 9.0. This problem didn't happen with the 2.4 kernel, only with 2.6. I've tried Kraxel's 2.6 kernel RPM, and also a kernel I've compiled myself, and I get the same results with each. When I look at /var/log/boot.msg I see this line at the end, summing up the services which failed to start:
This problem with kernel 2.6 went away for me after I disabled kernel preemption. It is likely a race condition in startproc. Is there a patch available for it?
-- Eric
I think I still see the problem with preemption disabled, but I shall recheck. Some time ago they said it would be fixed, but hasn't been, may be time to drop another hint to the kernel mailing list. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
On Thursday 25 March 2004 13:27, Eric Bloodworth wrote:
Why is it that I see lots of 'failed' messages when I boot my SuSE Linux laptop, but the services which are reported to have failed are actually up and running just fine?
I'm running SuSE 9.0. This problem didn't happen with the 2.4 kernel, only with 2.6. I've tried Kraxel's 2.6 kernel RPM, and also a kernel I've compiled myself, and I get the same results with each. When I look at /var/log/boot.msg I see this line at the end, summing up the services which failed to start:
This problem with kernel 2.6 went away for me after I disabled kernel preemption. It is likely a race condition in startproc. Is there a patch available for it?
-- Eric
It happens on 2.4 (mantel) kernels under SuSE 8.2 occasionally as well especially if there is a wireless nic involved. Services not started at runlevel 3 often are started by the time you get to runlevel 5. -- _____________________________________ John Andersen
participants (3)
-
Eric Bloodworth -
John Andersen -
Sid Boyce